Re: Confirmation of Fix for Bug 735199 and Karma for dracut

2011-09-02 Thread Masami Ichikawa
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://s

[Test-Announce] 2011-09-05 @ 15:00 UTC - Fedora QA Meeting (?)

2011-09-02 Thread Adam Williamson
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

Confirmation of Fix for Bug 735199 and Karma for dracut

2011-09-02 Thread Tim Flink
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

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Peter Gueckel
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)! -- tes

Re: lldpad consuming up to 65% of cpu

2011-09-02 Thread Chuck Anderson
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

Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login

2011-09-02 Thread Adam Williamson
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 gnom

Re: lldpad consuming up to 65% of cpu

2011-09-02 Thread Adam Williamson
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 henc

Re: F16 beta TC1 garbled graphical screen [workaround]

2011-09-02 Thread Clyde E. Kunkel
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 grap

Re: lldpad consuming up to 65% of cpu

2011-09-02 Thread Peter Gueckel
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

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Peter Gueckel
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

2011-09-02 Thread Adam Williamson
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 de

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Peter Gueckel
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 th

lldpad consuming up to 65% of cpu

2011-09-02 Thread Peter Gueckel
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

2011-09-02 Thread Branched Report
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)

Re: F16 beta TC1 garbled graphical screen [workaround]

2011-09-02 Thread Adam Williamson
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 ins

Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login

2011-09-02 Thread Bill Nottingham
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. > > Anyb

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

2011-09-02 Thread Adam Williamson
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 gri

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

2011-09-02 Thread Bruno Wolff III
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 rawh

Re: [Bug 727814] F16 Alpha TC1 installer crash | LUKSError: luks device not configured

2011-09-02 Thread Michael Schwendt
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 the

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

2011-09-02 Thread Jonathan Corbet
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,

Re: F16 beta TC1 garbled graphical screen [workaround]

2011-09-02 Thread Jurgen Kramer
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=ve

Re: [Bug 727814] F16 Alpha TC1 installer crash | LUKSError: luks device not configured

2011-09-02 Thread Tim Flink
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

Re: Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login

2011-09-02 Thread Matthias Clasen
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. > > A

rawhide report: 20110902 changes

2011-09-02 Thread Rawhide Report
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

F16 beta TC1 garbled graphical screen

2011-09-02 Thread Jurgen Kramer
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

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Joachim Backes
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 happ

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Joachim Backes
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? Confirm

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Tom H
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 a

Re: F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Jóhann B. Guðmundsson
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

F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

2011-09-02 Thread Joachim Backes
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 Signatu

Update to gdm-3.1.90-1 and/or gdm-plugin-fingerprint-3.1.90-1 break the gdm login

2011-09-02 Thread Joachim Backes
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.d

Re: New BugZapper Introduction

2011-09-02 Thread Matej Cepl
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