Re: Confirmation of Fix for Bug 735199 and Karma for dracut
on 09/03/2011 11:51 AM, Tim Flink wrote: > Bug 735199 [1] is a beta blocker that causes intermittent problems with > installers. > > I made a test boot.iso with the new dracut-013-8 package. It would be > great if we could get some confirmation of the fix and karma for > dracut [2]. > > https://s3.amazonaws.com/fedoratestimages/dracut_20110902/boot-x86_64.iso > https://s3.amazonaws.com/fedoratestimages/dracut_20110902/boot-x86_64.iso.sha256 > > Thanks, I tested ten times with the iso and didn't reproduce rhbz 735199. I gave +1 karma. Cheers, -- Masami Ichikawa gmail: masami...@gmail.com Fedora project: mas...@fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2011-09-05 @ 15:00 UTC - Fedora QA Meeting (?)
WHAT: Fedora QA Meeting WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT) WHERE: #fedora-meeting So it's meeting time again on Monday, except that it's a vacation in both Canada and the U.S., so myself and Tim Flink, and perhaps some of our North American community members, won't be present. If someone else would like to step up and run the meeting, that'd be great. There aren't any big agenda topics that I'm aware of, but it'd be good to follow up on the previous meeting and check in on how we're looking for Beta. Also, it's graphics test week - I haven't done much prep, but I'll try and get the pages polished and announcements put out over the weekend. If anyone has anything to add to the agenda, please reply to this mail, and whoever ends up running the meeting will add it. Thanks! Proposed agenda: * Previous meeting follow-up (https://fedoraproject.org/wiki/QA/Meetings/20110829) * Beta preparation * Graphics test week * AutoQA update * Open discussion -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Confirmation of Fix for Bug 735199 and Karma for dracut
Bug 735199 [1] is a beta blocker that causes intermittent problems with installers. I made a test boot.iso with the new dracut-013-8 package. It would be great if we could get some confirmation of the fix and karma for dracut [2]. https://s3.amazonaws.com/fedoratestimages/dracut_20110902/boot-x86_64.iso https://s3.amazonaws.com/fedoratestimages/dracut_20110902/boot-x86_64.iso.sha256 Thanks, Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=735199 [2] https://admin.fedoraproject.org/updates/dracut-013-8.fc16 signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
Peter Gueckel wrote: > Joachim Backes wrote: >> Anybody has the same issue? > Any ideas how to get grub installed properly...? Many hours of work, my desktop computer is back. I don't care to do that agian (and don't ask me what I did, because I couldn't say, in any sensible order)! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: lldpad consuming up to 65% of cpu
On Fri, Sep 02, 2011 at 02:10:49PM -0700, Adam Williamson wrote: > On Fri, 2011-09-02 at 11:06 -0600, Peter Gueckel wrote: > > Adam Williamson wrote: > > > > > so if you have anaconda installed, you can > > probably > > > just remove it, remove fcoe-utils and > > lldpad, and be happy. > > > > I installed from alive CD, so I think that is > > why anaconda is installed, and hence, with > > it, as you said, all of the other stuff. > > > > I will uninstall as per your advice. Thanks > > Looks like there's a couple of bugs for this too: > > https://bugzilla.redhat.com/show_bug.cgi?id=701943 > https://bugzilla.redhat.com/show_bug.cgi?id=701999 And: https://bugzilla.redhat.com/show_bug.cgi?id=720080 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login
On Fri, 2011-09-02 at 09:41 -0400, Matthias Clasen wrote: > On Fri, 2011-09-02 at 10:37 +0200, Joachim Backes wrote: > > Hi, > > > > after having updated to gdm-3.1.90-1 and gdm-plugin-fingerprint-3.1.90-1 > > the login fails (error: "Oh no! Something has gone wrong"). > > > > Disabling the gnome-shell-extensions (as proposed) is useless in this > > situation. > > > > Anybody has the same issue? > > > > Hard to say because you didn't really describe the issue in sufficient > detail... > > That being said, there is one bug report where turning off selinux > enforcing made a similar crash go away. isn't this likely to be the missing dep thing notting(?) was hitting in #fedora-desktop yesterday? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: lldpad consuming up to 65% of cpu
On Fri, 2011-09-02 at 11:06 -0600, Peter Gueckel wrote: > Adam Williamson wrote: > > > so if you have anaconda installed, you can > probably > > just remove it, remove fcoe-utils and > lldpad, and be happy. > > I installed from alive CD, so I think that is > why anaconda is installed, and hence, with > it, as you said, all of the other stuff. > > I will uninstall as per your advice. Thanks Looks like there's a couple of bugs for this too: https://bugzilla.redhat.com/show_bug.cgi?id=701943 https://bugzilla.redhat.com/show_bug.cgi?id=701999 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16 beta TC1 garbled graphical screen [workaround]
On 09/02/2011 12:21 PM, Adam Williamson wrote: > On Fri, 2011-09-02 at 17:02 +0200, Jurgen Kramer wrote: >> On Fri, 2011-09-02 at 11:53 +0200, Jurgen Kramer wrote: >>> When I get past the current dracut/squashfs problems (BZ#735199) >>> (workaround maxcpus=1 works for me). I only get a garbled graphical >>> screen so I cannot continue with the installation. >>> anaconda textmode is no longer there and xdriver=vesa gives the same >>> garbled screen. >>> >>> All F16 alpha rc's and alpha worked fine with the graphical installer. >>> Did something change here? >>> >>> btw this is when booting through EFI. Legacy boot works. >>> >> The garbled screen at boot is still there, but when booting in EFI mode >> with maxcpus=1 and a bit more patience (wait for hardware), anaconda >> gets to the normal graphical install screen and I can make my way >> through a the installation. > > Oh, so it comes up garbled, then after a while resolves itself? > Interesting. What hardware? I have seen something similar, but not on every boot. radeon rv630 -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: lldpad consuming up to 65% of cpu
Adam Williamson wrote: > so if you have anaconda installed, you can probably > just remove it, remove fcoe-utils and lldpad, and be happy. I installed from alive CD, so I think that is why anaconda is installed, and hence, with it, as you said, all of the other stuff. I will uninstall as per your advice. Thanks :-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
Joachim Backes wrote: > after each kernel update I burn a boot cd Explain how you do this! It wastes a lot of CDs, but saves a lot of wasted time trying to rescue a system. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: lldpad consuming up to 65% of cpu
On Fri, 2011-09-02 at 10:27 -0600, Peter Gueckel wrote: > what is this lldpad daemonand why does it run > continually for days on end without ever > terminating and consume up to 65% of my > laptop's cpu? You probably don't need it; it's for enterprise stuff. fcoe-utils seems to have grown a dependency on it, which is why it's being pulled into people's systems lately. On my system, anaconda is the only thing that requires fcoe-utils, so if you have anaconda installed, you can probably just remove it, remove fcoe-utils and lldpad, and be happy. It's probably a bug that it's thrashing resources on systems where it can't *do* anything useful, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
Joachim Backes wrote: > Anybody has the same issue? Yes, please HELP! :-) I am unable to boot my desktop computer. I just get a grub rescue command prompt and no grub commands except set seem to be recognized. I cannot boot into Fedora 15 or Fedora 16 alpha. I am trying to fix by running the boot.fedora.iso CD, but I am not hopeful that this is the solution I want. Any ideas how to get grub installed properly on a system that only had grub rescue prompt and will not boot into any installed fedoras? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
lldpad consuming up to 65% of cpu
what is this lldpad daemonand why does it run continually for days on end without ever terminating and consume up to 65% of my laptop's cpu? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-16 Branched report: 20110902 changes
Compose started at Fri Sep 2 13:15:30 UTC 2011 Broken deps for x86_64 -- 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpagent.so.25()(64bit) 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpmibs.so.25()(64bit) 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmp.so.25()(64bit) acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell) airrac-0.1.0-2.fc16.i686 requires libstdair.so.0.36 airrac-0.1.0-2.fc16.i686 requires libstdairuicl.so.0.36 airrac-0.1.0-2.fc16.x86_64 requires libstdairuicl.so.0.36()(64bit) airrac-0.1.0-2.fc16.x86_64 requires libstdair.so.0.36()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libcamel-1.2.so.26()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libedataserverui-3.0.so.0()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libecal-1.2.so.9()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libedataserver-1.2.so.14()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libebook-1.2.so.11()(64bit) 1:anerley-0.3.0-1.fc16.i686 requires libedataserver-1.2.so.14 1:anerley-0.3.0-1.fc16.i686 requires libebook-1.2.so.11 1:anerley-0.3.0-1.fc16.x86_64 requires libebook-1.2.so.11()(64bit) 1:anerley-0.3.0-1.fc16.x86_64 requires libedataserver-1.2.so.14()(64bit) assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit) awn-extras-applets-0.4.2-0.1.bzr1523.fc16.x86_64 requires libgnome-menu.so.2()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires rvm-tools coda-server-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libebook-1.2.so.10()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires gnome-python2-applet deskbar-applet-2.32.0-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libedataserver-1.2.so.14()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave emerillon-0.1.2-17.fc16.x86_64 requires libethos-ui-1.0.so.0()(64bit) emerillon-0.1.2-17.fc16.x86_64 requires libethos-1.0.so.0()(64bit) evolution-rss-0.2.90-25.20110716git.fc16.x86_64 requires libedataserver-1.2.so.14()(64bit) evolution-rss-0.2.90-25.20110716git.fc16.x86_64 requires libebook-1.2.so.11()(64bit) exaile-0.3.2.1-1.fc16.noarch requires hal fawkes-guis-0.4.2-4.fc16.i686 requires libgvc.so.5 fawkes-guis-0.4.2-4.fc16.i686 requires libcdt.so.4 fawkes-guis-0.4.2-4.fc16.i686 requires libgraph.so.4 fawkes-guis-0.4.2-4.fc16.x86_64 requires libgvc.so.5()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libcdt.so.4()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libgraph.so.4()(64bit) fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires libboost_signals-mt.so.1.46.1()(64bit) fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires libboost_thread-mt.so.1.46.1()(64bit) fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires libgeos-3.2.1.so()(64bit) ffgtk-plugin-evolution-0.7.94-5.fc16.x86_64 requires libedataserver-1.2.so.14()(64bit) ffgtk-plugin-evolution-0.7.94-5.fc16.x86_64 requires libebook-1.2.so.11()(64bit) file-browser-applet-0.6.6-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) flaw-1.2.4-2.fc15.x86_64 requires libSDL_gfx.so.0()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfl
Re: F16 beta TC1 garbled graphical screen [workaround]
On Fri, 2011-09-02 at 17:02 +0200, Jurgen Kramer wrote: > On Fri, 2011-09-02 at 11:53 +0200, Jurgen Kramer wrote: > > When I get past the current dracut/squashfs problems (BZ#735199) > > (workaround maxcpus=1 works for me). I only get a garbled graphical > > screen so I cannot continue with the installation. > > anaconda textmode is no longer there and xdriver=vesa gives the same > > garbled screen. > > > > All F16 alpha rc's and alpha worked fine with the graphical installer. > > Did something change here? > > > > btw this is when booting through EFI. Legacy boot works. > > > The garbled screen at boot is still there, but when booting in EFI mode > with maxcpus=1 and a bit more patience (wait for hardware), anaconda > gets to the normal graphical install screen and I can make my way > through a the installation. Oh, so it comes up garbled, then after a while resolves itself? Interesting. What hardware? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login
Joachim Backes (joachim.bac...@rhrk.uni-kl.de) said: > Hi, > > after having updated to gdm-3.1.90-1 and > gdm-plugin-fingerprint-3.1.90-1 the login fails (error: "Oh no! > Something has gone wrong"). > > Disabling the gnome-shell-extensions (as proposed) is useless in > this situation. > > Anybody has the same issue? Some things I ran into yesterday: - make sure you have caribou installed (this should be added to requirements in a new build) - make sure you have libgee-devel installed (this should be fixed in a new build so you don't need this package) Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)
On Fri, 2011-09-02 at 09:27 -0600, Jonathan Corbet wrote: > > The questions is how do we want to handle this? At least we should > > release note this I guess, but perhaps we can do something smarter? > > Perhaps the first thing to do is to try to figure out if it's only me. > Nobody else has griped on the Rawhide front, but, then, I think I may be > about the only Rawhide user left (and people keep telling me that I > shouldn't be there either). There are other people using Rawhide, you're being somewhat exaggerated to. And the same update has been build for F16, and went into updates-testing two days ago: https://admin.fedoraproject.org/updates/bluez-4.96-2.fc16 - so F16 users should have it now too. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)
On Fri, Sep 02, 2011 at 09:27:12 -0600, Jonathan Corbet wrote: > > Nobody else has griped on the Rawhide front, but, then, I think I may be > about the only Rawhide user left (and people keep telling me that I > shouldn't be there either). If it's only me I'll figure out how to put I use rawhide on my main home machine a good chunk of the time. Even with branched available, there is stuff I want to test in rawhide first that I deploy. Also I like to get an early look at new kernels, since I seem to have a higher than normal breakage rate for new kernels. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Bug 727814] F16 Alpha TC1 installer crash | LUKSError: luks device not configured
On Fri, 2 Sep 2011 08:34:49 -0600, TF (Tim) wrote: > > > https://bugzilla.redhat.com/show_bug.cgi?id=727814 > True, both ways should work but it doesn't really seem that common of a > use case since (we thought) most people would be either ignoring all of > their encrypted partitions or using them. As I read it, you have to > enter a password for some but not all of your encrypted partitions. My bad. I've added a comment to the ticket. Cancelling all passphrase prompts _or_ filling in just one passphrase prompt made Anaconda crash. Only way to proceed has been to answer all passphrase prompts. -- Fedora release 16 (Verne) - Linux 3.1.0-0.rc4.git0.0.fc16.x86_64 loadavg: 0.02 0.20 0.19 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)
On Fri, 02 Sep 2011 09:18:31 +0200 Hans de Goede wrote: > Which is in essence the problem you are seeing here Jonathan, after > my bluez update, your bluetooth dongle is actually being out into > HCI mode, so that it can for example also be used to sync with your > phone, use a bluetooth headset, etc. IOW this is a feature not a bug > but this does mean that in order to use your bluetooth mouse / > keyboard, you need to explicitly pair them with the bluetooth HCI once, > which will require the use of a regular usb keyboard, which is, erm, > not so good, one could even argue this is a bug after all. I guess I would argue that the vast majority of users who get one of these Logitech keyboards simply want a keyboard; they don't really care that they got a general-purpose Bluetooth adapter in the deal. So breaking that by default doesn't necessarily seem like the right idea. That said... > This also brings us back to my: "I'm really really surprised about the > "has Just Worked for years" bit", since we've been shipping hid2hci > + udev rules for years (and this issue has been reported by others long > before). ...it sounds like it's maybe been broken in this way for a while? My machine has been riding the Rawhide train for years, it's possible it doesn't correspond to what I'd get if I just dumped F15 onto it. > The questions is how do we want to handle this? At least we should > release note this I guess, but perhaps we can do something smarter? Perhaps the first thing to do is to try to figure out if it's only me. Nobody else has griped on the Rawhide front, but, then, I think I may be about the only Rawhide user left (and people keep telling me that I shouldn't be there either). If it's only me I'll figure out how to put the keyboard into a mode where it's agreeable to pairing, grumble for a moment, and get on with my life. If others are affected, it would be nice to detect the situation and put up a little warning, preferably on the login screen. Not sure how easy that would be to do. Thanks for the explanation, jon -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16 beta TC1 garbled graphical screen [workaround]
On Fri, 2011-09-02 at 11:53 +0200, Jurgen Kramer wrote: > When I get past the current dracut/squashfs problems (BZ#735199) > (workaround maxcpus=1 works for me). I only get a garbled graphical > screen so I cannot continue with the installation. > anaconda textmode is no longer there and xdriver=vesa gives the same > garbled screen. > > All F16 alpha rc's and alpha worked fine with the graphical installer. > Did something change here? > > btw this is when booting through EFI. Legacy boot works. > The garbled screen at boot is still there, but when booting in EFI mode with maxcpus=1 and a bit more patience (wait for hardware), anaconda gets to the normal graphical install screen and I can make my way through a the installation. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Bug 727814] F16 Alpha TC1 installer crash | LUKSError: luks device not configured
On Fri, 2 Sep 2011 02:27:15 -0400 (EDT) Kamil Paral wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=727814 > > > > --- Comment #8 from Tim Flink 2011-09-01 > > 13:18:54 EDT --- Discussed in the 2011-08-26 blocker review > > meeting. Rejected as a Fedora 16 beta blocker because it doesn't > > violate any of the beta release criteria [1]. > > > > Accepted as NTH because it's annoying and a fix is ready. > > > > [1] https://fedoraproject.org/wiki/Fedora_16_Beta_Release_Criteria > > I don't think we should mark any installer crashes as non-blockers > when there is a good chance users would hit it. I believe this > particular bug should have been an Alpha blocker: > > "The installer must be able to complete an installation using the > entire disk, existing free space, or existing Linux partitions > methods, with or without encryption or LVM enabled" > https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria > > Whether I do or don't provide the password to my existing encrypted > partitions doesn't really matter, both ways are very probable, both > ways should work. At least in my opinion. True, both ways should work but it doesn't really seem that common of a use case since (we thought) most people would be either ignoring all of their encrypted partitions or using them. As I read it, you have to enter a password for some but not all of your encrypted partitions. The question comes down to - would this bug be worth holding up the entire alpha release until it was fixed? If it was final, maybe but not alpha, in my opinion. Looking at the logs from the blocker review meeting when we decided to make it NTH instead of blocker - it's the same thing but since a fix is available, we didn't deliberate on it too much since that would be more academic than anything. It's reported to be fixed in anaconda 16.15-1 and should be fixed. Are you still hitting it? As a side note, you don't have to actually be at the blocker bug review meeting to vote. You can go through the blocker bugs and put your vote and concerns in the bug comments - we're trying to do that more anyways. Thanks, Tim signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login
On Fri, 2011-09-02 at 10:37 +0200, Joachim Backes wrote: > Hi, > > after having updated to gdm-3.1.90-1 and gdm-plugin-fingerprint-3.1.90-1 > the login fails (error: "Oh no! Something has gone wrong"). > > Disabling the gnome-shell-extensions (as proposed) is useless in this > situation. > > Anybody has the same issue? > Hard to say because you didn't really describe the issue in sufficient detail... That being said, there is one bug report where turning off selinux enforcing made a similar crash go away. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20110902 changes
Compose started at Fri Sep 2 08:15:27 UTC 2011 Broken deps for x86_64 -- FlightGear-2.0.0-6.fc16.x86_64 requires libosgViewer.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgUtil.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgText.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgSim.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgParticle.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgGA.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgFX.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgDB.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosg.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libOpenThreads.so.11()(64bit) SimGear-2.0.0-6.fc16.i686 requires libosgParticle.so.74 SimGear-2.0.0-6.fc16.i686 requires libosgDB.so.74 SimGear-2.0.0-6.fc16.i686 requires libosg.so.74 SimGear-2.0.0-6.fc16.i686 requires libOpenThreads.so.11 SimGear-2.0.0-6.fc16.x86_64 requires libosgParticle.so.74()(64bit) SimGear-2.0.0-6.fc16.x86_64 requires libosgDB.so.74()(64bit) SimGear-2.0.0-6.fc16.x86_64 requires libosg.so.74()(64bit) SimGear-2.0.0-6.fc16.x86_64 requires libOpenThreads.so.11()(64bit) acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell) assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit) awn-extras-applets-0.4.2-0.1.bzr1523.fc16.x86_64 requires libgnome-menu.so.2()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) caribou-0.3.5-1.fc16.i686 requires libgee.so.2 caribou-0.3.5-1.fc16.x86_64 requires libgee.so.2()(64bit) 1:cheese-3.0.2-2.fc16.x86_64 requires libgee.so.2()(64bit) 1:cheese-libs-3.0.2-2.fc16.i686 requires libgee.so.2 1:cheese-libs-3.0.2-2.fc16.x86_64 requires libgee.so.2()(64bit) cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires rvm-tools coda-server-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libedataserver-1.2.so.14()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libebook-1.2.so.10()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires gnome-python2-applet dh-make-0.55-3.fc15.noarch requires debhelper ease-0.4-7.fc17.i686 requires libgee.so.2 ease-0.4-7.fc17.x86_64 requires libgee.so.2()(64bit) ease-devel-0.4-7.fc17.i686 requires pkgconfig(gee-1.0) ease-devel-0.4-7.fc17.x86_64 requires pkgconfig(gee-1.0) ekiga-3.3.1-3.fc17.x86_64 requires libpt.so.2.10.1()(64bit) ekiga-3.3.1-3.fc17.x86_64 requires libcamel-1.2.so.28()(64bit) emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave emerillon-0.1.2-17.fc16.x86_64 requires libethos-ui-1.0.so.0()(64bit) emerillon-0.1.2-17.fc16.x86_64 requires libethos-1.0.so.0()(64bit) empathy-3.1.90.1-2.fc17.x86_64 requires libgee.so.2()(64bit) fawkes-core-0.4.2-4.fc16.i686 requires libopencv_video.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_objdetect.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_ml.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_legacy.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_imgproc.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_highgui.so.2.2 fawkes-core-0.4.2-4.fc16.i68
F16 beta TC1 garbled graphical screen
When I get past the current dracut/squashfs problems (BZ#735199) (workaround maxcpus=1 works for me). I only get a garbled graphical screen so I cannot continue with the installation. anaconda textmode is no longer there and xdriver=vesa gives the same garbled screen. All F16 alpha rc's and alpha worked fine with the graphical installer. Did something change here? btw this is when booting through EFI. Legacy boot works. Jurgen -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
On 09/02/2011 11:01 AM, Tom H wrote: On Fri, Sep 2, 2011 at 4:45 AM, Joachim Backes wrote: After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot (file not found). Getting rid from this by re-installing the bootloader to /dev/sda. Anybody has the same issue? Yes. Just happened to me. "/boot/grub2/" is almost empty after the upgrade except for "grub.cfg", "devicemap.lst.anacbak", and "locale/". "grub2-install /dev/sda /dev/sdb" while booted from Anaconda's rescue mode repopulated the directory. Not me: after each kernel update I burn a boot cd, so I could boot from this cd to a fully operating F16 without usage of the rescue cd/anaconda. I can't say that /boot/grub2 was empty before running grub2-install. Then running grub2-install rewrote the bootloader. There's a part of the preuninstall scriplet that deletes all ".mod", ".img" and ".lst" files from "/boot/grub2/" that might somehow be responsible. -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
On 09/02/2011 10:51 AM, "Jóhann B. Guðmundsson" wrote: On 09/02/2011 08:45 AM, Joachim Backes wrote: After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot (file not found). Getting rid from this by re-installing the bootloader to /dev/sda. Anybody has the same issue? Confirmed file a bug and add it to the blocker bug list and comment if you have edited the config files or not. Done: BZ 735301 -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
On Fri, Sep 2, 2011 at 4:45 AM, Joachim Backes wrote: > > After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot > (file not found). Getting rid from this by re-installing the bootloader to > /dev/sda. > > Anybody has the same issue? Yes. Just happened to me. "/boot/grub2/" is almost empty after the upgrade except for "grub.cfg", "devicemap.lst.anacbak", and "locale/". "grub2-install /dev/sda /dev/sdb" while booted from Anaconda's rescue mode repopulated the directory. There's a part of the preuninstall scriplet that deletes all ".mod", ".img" and ".lst" files from "/boot/grub2/" that might somehow be responsible. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
On 09/02/2011 08:45 AM, Joachim Backes wrote: > After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to > boot (file not found). Getting rid from this by re-installing the > bootloader to /dev/sda. > > Anybody has the same issue? Confirmed file a bug and add it to the blocker bug list and comment if you have edited the config files or not. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot
After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot (file not found). Getting rid from this by re-installing the bootloader to /dev/sda. Anybody has the same issue? -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login
Hi, after having updated to gdm-3.1.90-1 and gdm-plugin-fingerprint-3.1.90-1 the login fails (error: "Oh no! Something has gone wrong"). Disabling the gnome-shell-extensions (as proposed) is useless in this situation. Anybody has the same issue? -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
Dne 2.9.2011 07:33, Gerard Snitselaar napsal(a): > My day job has been working with Unix since 2000 and mostly Linux since 2004, > performing fault analysis of kernel dumps or determining if bugs are in our > code or somewhere else in Red Hat, and fixing bugs in our code. So I spend a > fair amount of time with c code, and have spent too much time looking at > stacks > and disassembled code. > > I'm 39 and live in Phoenix, Arizona. I have a wife, a daughter who will soon > be 2, > and another child on the way. I look forward to working with everyone and > helping out. Wov! Congrats on the family! (and yes, bug triaging is much more peaceful than changing the diapers ;)). Feel free to ping me on #fedora-bugzappers anytime (I am usually around CET business hours and in the evening). We also maintain (well, more or less maintain) https://fedoraproject.org/wiki/BugZappers with all information we have for budding bug zappers (particularly https://fedoraproject.org/wiki/BugZappers/Joining is meant to be a good start page). Welcome on board! Matěj -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
