No sound in rawhide
Hi, Prior to the big push to f12, my system had full audio. No problems. Lovely, lovely sounds. For some reason, alsa and pulseaudio are completely failing to pick up my sound card (either the onboard one or my soundblaster). This is despite them both being listed on lspci and lsmod. Any ideas on getting this to work again? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
No sound in rawhide
Sooo, I thought I saw mention about sound with current rawhide or close. Mine is just the ac97 or whatever built into the motherboard and after a straight up upgrade from F11 to rawhide it stopped working. I take it known problem already? Have anything to do with the boxes on the panel in the notification area being there instead of the device icons? -- Mike Chambers Madisonville, KY Fedora Project - Bugzapper, Tester, User, etc.. miketc...@fedoraproject.org -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
Hi. On Mon, 15 Jun 2009 13:09:27 +0100, Paul wrote: > Any ideas on getting this to work again? On my system all sound files (/dev/snd) were owned by root instead of the user logged into X. Don't know who's responsible for fixing that. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Mon, 2009-06-15 at 13:09 +0100, Paul wrote: > Hi, > > Prior to the big push to f12, my system had full audio. No problems. > Lovely, lovely sounds. > > For some reason, alsa and pulseaudio are completely failing to pick up > my sound card (either the onboard one or my soundblaster). This is > despite them both being listed on lspci and lsmod. > > Any ideas on getting this to work again? As per usual, pulseaudio debug output is a requirement. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Mon, Jun 15, 2009 at 4:23 PM, Ralf Ertzinger wrote: > Hi. > > On Mon, 15 Jun 2009 13:09:27 +0100, Paul wrote: > >> Any ideas on getting this to work again? > > On my system all sound files (/dev/snd) were owned by root instead of the > user logged into X. Don't know who's responsible for fixing that. ConsoleKit / hal -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
ti., 16.06.2009 kl. 11.17 +0100, skrev Bastien Nocera: > On Mon, 2009-06-15 at 13:09 +0100, Paul wrote: > > Hi, > > > > Prior to the big push to f12, my system had full audio. No problems. > > Lovely, lovely sounds. > > > > For some reason, alsa and pulseaudio are completely failing to pick up > > my sound card (either the onboard one or my soundblaster). This is > > despite them both being listed on lspci and lsmod. > > > > Any ideas on getting this to work again? > > As per usual, pulseaudio debug output is a requirement. > I found that pulseaudio -k && pulseaudio "fixed" it for me after chown on /dev/snd/* which had root.audio ownership. I see this error when starting pulseaudio though: [kmar...@nc6400 ~]$ pulseaudio E: bluetooth-util.c: Error from ListAdapters reply:org.freedesktop.DBus.Error.ServiceUnknown Cheers Kjartan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, 2009-06-17 at 13:51 +0200, Kjartan Maraas wrote: > ti., 16.06.2009 kl. 11.17 +0100, skrev Bastien Nocera: > > On Mon, 2009-06-15 at 13:09 +0100, Paul wrote: > > > Hi, > > > > > > Prior to the big push to f12, my system had full audio. No problems. > > > Lovely, lovely sounds. > > > > > > For some reason, alsa and pulseaudio are completely failing to pick up > > > my sound card (either the onboard one or my soundblaster). This is > > > despite them both being listed on lspci and lsmod. > > > > > > Any ideas on getting this to work again? > > > > As per usual, pulseaudio debug output is a requirement. > > > I found that pulseaudio -k && pulseaudio "fixed" it for me after chown > on /dev/snd/* which had root.audio ownership. I see this error when > starting pulseaudio though: > > [kmar...@nc6400 ~]$ pulseaudio > E: bluetooth-util.c: Error from ListAdapters > reply:org.freedesktop.DBus.Error.ServiceUnknown That means that bluetoothd isn't running, which should be fine. There are some known problems with PulseAudio's Bluetooth plugin handling of presense/absence of bluetoothd. This was discussed in another thread on this ML. Cheers -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, 17.06.09 13:51, Kjartan Maraas (kmar...@broadpark.no) wrote: > > ti., 16.06.2009 kl. 11.17 +0100, skrev Bastien Nocera: > > On Mon, 2009-06-15 at 13:09 +0100, Paul wrote: > > > Hi, > > > > > > Prior to the big push to f12, my system had full audio. No problems. > > > Lovely, lovely sounds. > > > > > > For some reason, alsa and pulseaudio are completely failing to pick up > > > my sound card (either the onboard one or my soundblaster). This is > > > despite them both being listed on lspci and lsmod. > > > > > > Any ideas on getting this to work again? > > > > As per usual, pulseaudio debug output is a requirement. > > > I found that pulseaudio -k && pulseaudio "fixed" it for me after chown > on /dev/snd/* which had root.audio ownership. I see this error when > starting pulseaudio though: Hmm, if the permissions aren't set up correctly then this is some HAL ACL handling brokeness. Wouldn't be the first one. > [kmar...@nc6400 ~]$ pulseaudio > E: bluetooth-util.c: Error from ListAdapters > reply:org.freedesktop.DBus.Error.ServiceUnknown That's a missing bluetoothd. This shouldn't be fatal though, or is it? Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, Jun 17, 2009 at 01:51:37PM +0200, Kjartan Maraas wrote: > ti., 16.06.2009 kl. 11.17 +0100, skrev Bastien Nocera: > > On Mon, 2009-06-15 at 13:09 +0100, Paul wrote: > > > Hi, > > > > > > Prior to the big push to f12, my system had full audio. No problems. > > > Lovely, lovely sounds. > > > > > > For some reason, alsa and pulseaudio are completely failing to pick up > > > my sound card (either the onboard one or my soundblaster). This is > > > despite them both being listed on lspci and lsmod. > > > > > > Any ideas on getting this to work again? > > > > As per usual, pulseaudio debug output is a requirement. > > > I found that pulseaudio -k && pulseaudio "fixed" it for me after chown > on /dev/snd/* which had root.audio ownership. I see this error when > starting pulseaudio though: > > [kmar...@nc6400 ~]$ pulseaudio > E: bluetooth-util.c: Error from ListAdapters > reply:org.freedesktop.DBus.Error.ServiceUnknown > > Cheers > Kjartan Hmm, I just always figured I was supposed to add myself to the audio group. So these files are supposed to be owned by my local user account when I log in eh? Ray -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, Jun 17, 2009 at 7:25 AM, Ray Van Dolson wrote: > Hmm, I just always figured I was supposed to add myself to the audio > group. So these files are supposed to be owned by my local user > account when I log in eh? No... you should be added to the acl list associated to the device if you are the physical console user as per the authorization policy managed by PolicyKit. This it how it works from at least F10 onward. Mucking around with file ownership directly is "old think." The system scripts associated with pam use to do that on user login and logout...but has been replaced with the more flexible solution involving acls that PolicyKit based hardware access authorization makes use of. for example on the F10 system I'm on right now: ls -la /dev/snd/seq crw-rw+ 1 root root 116, 3 2009-06-17 07:07 /dev/snd/seq getfacl /dev/dsp # file: dev/snd/seq # owner: root # group: root user::rw- user:myuser:rw- group::rw- mask::rw- other::--- I do not own the file in the traditional Unix permissions sense. But I am listed in the acl list with read write access. If your user is not in the acl list, something misfired in the area of the PolicyKit based authorization handling. -jef -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, Jun 17, 2009 at 8:06 AM, Jeff Spaleta wrote: > getfacl /dev/dsp typo: that should have been .dev./snd/seq not /dev/dsp the getfacl output cut and paste was correct for /dev/snd/seq -jef -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Wed, Jun 17, 2009 at 08:06:36AM -0800, Jeff Spaleta wrote: > On Wed, Jun 17, 2009 at 7:25 AM, Ray Van Dolson wrote: > > Hmm, I just always figured I was supposed to add myself to the audio > > group. So these files are supposed to be owned by my local user > > account when I log in eh? > > No... you should be added to the acl list associated to the device if > you are the physical console user as per the authorization policy > managed by PolicyKit. This it how it works from at least F10 onward. > Mucking around with file ownership directly is "old think." The system > scripts associated with pam use to do that on user login and > logout...but has been replaced with the more flexible solution > involving acls that PolicyKit based hardware access authorization > makes use of. > > > for example on the F10 system I'm on right now: > ls -la /dev/snd/seq > crw-rw+ 1 root root 116, 3 2009-06-17 07:07 /dev/snd/seq > > > getfacl /dev/dsp > # file: dev/snd/seq > # owner: root > # group: root > user::rw- > user:myuser:rw- > group::rw- > mask::rw- > other::--- > > I do not own the file in the traditional Unix permissions sense. But I > am listed in the acl list with read write access. If your user is not > in the acl list, something misfired in the area of the PolicyKit based > authorization handling. Good to know. I've checked the acl list in the past and definitely wasn't a member. I'll have to remove myself from audio and see if I can track this down. Thanks, Ray -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
on., 17.06.2009 kl. 11.44 -0700, skrev Ray Van Dolson: > On Wed, Jun 17, 2009 at 08:06:36AM -0800, Jeff Spaleta wrote: > > On Wed, Jun 17, 2009 at 7:25 AM, Ray Van Dolson wrote: > > > Hmm, I just always figured I was supposed to add myself to the audio > > > group. So these files are supposed to be owned by my local user > > > account when I log in eh? > > > > No... you should be added to the acl list associated to the device if > > you are the physical console user as per the authorization policy > > managed by PolicyKit. This it how it works from at least F10 onward. > > Mucking around with file ownership directly is "old think." The system > > scripts associated with pam use to do that on user login and > > logout...but has been replaced with the more flexible solution > > involving acls that PolicyKit based hardware access authorization > > makes use of. > > > > > > for example on the F10 system I'm on right now: > > ls -la /dev/snd/seq > > crw-rw+ 1 root root 116, 3 2009-06-17 07:07 /dev/snd/seq > > > > > > getfacl /dev/dsp > > # file: dev/snd/seq > > # owner: root > > # group: root > > user::rw- > > user:myuser:rw- > > group::rw- > > mask::rw- > > other::--- > > > > I do not own the file in the traditional Unix permissions sense. But I > > am listed in the acl list with read write access. If your user is not > > in the acl list, something misfired in the area of the PolicyKit based > > authorization handling. > > Good to know. I've checked the acl list in the past and definitely > wasn't a member. > > I'll have to remove myself from audio and see if I can track this down. > Did you find anything? I'm still seeing this problem with rawhide as of today. Cheers Kjartan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
i added myself to the pulse-access and audio group .. On Wed, Jul 8, 2009 at 7:43 AM, Kjartan Maraas wrote: > on., 17.06.2009 kl. 11.44 -0700, skrev Ray Van Dolson: > > On Wed, Jun 17, 2009 at 08:06:36AM -0800, Jeff Spaleta wrote: > > > On Wed, Jun 17, 2009 at 7:25 AM, Ray Van Dolson > wrote: > > > > Hmm, I just always figured I was supposed to add myself to the audio > > > > group. So these files are supposed to be owned by my local user > > > > account when I log in eh? > > > > > > No... you should be added to the acl list associated to the device if > > > you are the physical console user as per the authorization policy > > > managed by PolicyKit. This it how it works from at least F10 onward. > > > Mucking around with file ownership directly is "old think." The system > > > scripts associated with pam use to do that on user login and > > > logout...but has been replaced with the more flexible solution > > > involving acls that PolicyKit based hardware access authorization > > > makes use of. > > > > > > > > > for example on the F10 system I'm on right now: > > > ls -la /dev/snd/seq > > > crw-rw+ 1 root root 116, 3 2009-06-17 07:07 /dev/snd/seq > > > > > > > > > getfacl /dev/dsp > > > # file: dev/snd/seq > > > # owner: root > > > # group: root > > > user::rw- > > > user:myuser:rw- > > > group::rw- > > > mask::rw- > > > other::--- > > > > > > I do not own the file in the traditional Unix permissions sense. But I > > > am listed in the acl list with read write access. If your user is not > > > in the acl list, something misfired in the area of the PolicyKit based > > > authorization handling. > > > > Good to know. I've checked the acl list in the past and definitely > > wasn't a member. > > > > I'll have to remove myself from audio and see if I can track this down. > > > Did you find anything? I'm still seeing this problem with rawhide as of > today. > > Cheers > Kjartan > > > -- > fedora-devel-list mailing list > fedora-devel-list@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-list > -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
also renamed file /etc/pulse/default.pa.rpmnew to /etc/pulse/default.pa On Wed, Jul 8, 2009 at 8:22 AM, Sachin wrote: > i added myself to the pulse-access and audio group .. > > > On Wed, Jul 8, 2009 at 7:43 AM, Kjartan Maraas wrote: > >> on., 17.06.2009 kl. 11.44 -0700, skrev Ray Van Dolson: >> > On Wed, Jun 17, 2009 at 08:06:36AM -0800, Jeff Spaleta wrote: >> > > On Wed, Jun 17, 2009 at 7:25 AM, Ray Van Dolson >> wrote: >> > > > Hmm, I just always figured I was supposed to add myself to the audio >> > > > group. So these files are supposed to be owned by my local user >> > > > account when I log in eh? >> > > >> > > No... you should be added to the acl list associated to the device if >> > > you are the physical console user as per the authorization policy >> > > managed by PolicyKit. This it how it works from at least F10 onward. >> > > Mucking around with file ownership directly is "old think." The system >> > > scripts associated with pam use to do that on user login and >> > > logout...but has been replaced with the more flexible solution >> > > involving acls that PolicyKit based hardware access authorization >> > > makes use of. >> > > >> > > >> > > for example on the F10 system I'm on right now: >> > > ls -la /dev/snd/seq >> > > crw-rw+ 1 root root 116, 3 2009-06-17 07:07 /dev/snd/seq >> > > >> > > >> > > getfacl /dev/dsp >> > > # file: dev/snd/seq >> > > # owner: root >> > > # group: root >> > > user::rw- >> > > user:myuser:rw- >> > > group::rw- >> > > mask::rw- >> > > other::--- >> > > >> > > I do not own the file in the traditional Unix permissions sense. But I >> > > am listed in the acl list with read write access. If your user is not >> > > in the acl list, something misfired in the area of the PolicyKit based >> > > authorization handling. >> > >> > Good to know. I've checked the acl list in the past and definitely >> > wasn't a member. >> > >> > I'll have to remove myself from audio and see if I can track this down. >> > >> Did you find anything? I'm still seeing this problem with rawhide as of >> today. >> >> Cheers >> Kjartan >> >> >> -- >> fedora-devel-list mailing list >> fedora-devel-list@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-devel-list >> > > -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On 08/08/2009 06:15 PM, Mike Chambers wrote: I take it known problem already? Have anything to do with the boxes on the panel in the notification area being there instead of the device icons? Don't assume it is a known problem. Search bugzilla to see if you can find the same bug already filed, and if not, file one. ~spot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sat, 2009-08-08 at 17:15 -0500, Mike Chambers wrote: > Sooo, I thought I saw mention about sound with current rawhide or close. > Mine is just the ac97 or whatever built into the motherboard and after a > straight up upgrade from F11 to rawhide it stopped working. I take it > known problem already? Have anything to do with the boxes on the panel > in the notification area being there instead of the device icons? Indirectly, probably yes. There's a workaround for that known problem posted on rawhidewatch - restart notification-applet (or whatever the exact name is) until you get the icons instead of the boxes (can take over 20 tries, for me at least). At that point you'll probably see that the sound volume icon has the mute symbol on it. PA seems to still be initializing things at 0% volume when you first login. It is for me, anyway. I'm guessing that's the case for you. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, 2009-08-09 at 00:13 -0700, Adam Williamson wrote: > On Sat, 2009-08-08 at 17:15 -0500, Mike Chambers wrote: > > Sooo, I thought I saw mention about sound with current rawhide or close. > > Mine is just the ac97 or whatever built into the motherboard and after a > > straight up upgrade from F11 to rawhide it stopped working. I take it > > known problem already? Have anything to do with the boxes on the panel > > in the notification area being there instead of the device icons? > > Indirectly, probably yes. There's a workaround for that known problem > posted on rawhidewatch - restart notification-applet (or whatever the > exact name is) until you get the icons instead of the boxes (can take > over 20 tries, for me at least). At that point you'll probably see that > the sound volume icon has the mute symbol on it. PA seems to still be > initializing things at 0% volume when you first login. It is for me, > anyway. I'm guessing that's the case for you. The icon got to where it would be there at login, but it was muted. I would turn it up, and still no sound. Look a few moments later (if not seconds at times) and it would be muted again. -- Mike Chambers Madisonville, KY Fedora Project - Bugzapper, Tester, User, etc.. miketc...@fedoraproject.org -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, 2009-08-09 at 08:19 -0500, Mike Chambers wrote: > The icon got to where it would be there at login, but it was muted. I > would turn it up, and still no sound. Look a few moments later (if not > seconds at times) and it would be muted again. Different from my case, then. I'd say get PA logs (kill the session PA and run it at a console as 'pulseaudio -v') and file a bug. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
Hi. On Sun, 09 Aug 2009 00:13:40 -0700, Adam Williamson wrote > Indirectly, probably yes. There's a workaround for that known problem > posted on rawhidewatch - restart notification-applet (or whatever the > exact name is) until you get the icons instead of the boxes (can take > over 20 tries, for me at least). That's https://bugzilla.redhat.com/show_bug.cgi?id=510249, right? It currently blocks F12, shouldn't it block the aplha, too? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, 2009-08-09 at 19:51 +0200, Ralf Ertzinger wrote: > Hi. > > On Sun, 09 Aug 2009 00:13:40 -0700, Adam Williamson wrote > > > Indirectly, probably yes. There's a workaround for that known problem > > posted on rawhidewatch - restart notification-applet (or whatever the > > exact name is) until you get the icons instead of the boxes (can take > > over 20 tries, for me at least). > > That's https://bugzilla.redhat.com/show_bug.cgi?id=510249, right? > It currently blocks F12, shouldn't it block the aplha, too? No, we wouldn't consider it blocking the Alpha per the criteria (we consider only bugs that break the critical path - booting into X, getting a network connection and updating the system - as blockers for the Alpha, pretty much). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, Aug 9, 2009 at 9:11 PM, Adam Williamson wrote: > On Sun, 2009-08-09 at 19:51 +0200, Ralf Ertzinger wrote: >> Hi. >> >> On Sun, 09 Aug 2009 00:13:40 -0700, Adam Williamson wrote >> >> > Indirectly, probably yes. There's a workaround for that known problem >> > posted on rawhidewatch - restart notification-applet (or whatever the >> > exact name is) until you get the icons instead of the boxes (can take >> > over 20 tries, for me at least). >> >> That's https://bugzilla.redhat.com/show_bug.cgi?id=510249, right? >> It currently blocks F12, shouldn't it block the aplha, too? > > No, we wouldn't consider it blocking the Alpha per the criteria (we > consider only bugs that break the critical path - booting into X, > getting a network connection and updating the system - as blockers for > the Alpha, pretty much). + installing the system -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
Hi. On Sun, 09 Aug 2009 12:11:58 -0700, Adam Williamson wrote > No, we wouldn't consider it blocking the Alpha per the criteria (we > consider only bugs that break the critical path - booting into X, > getting a network connection and updating the system - as blockers for > the Alpha, pretty much). One may argue that being unable to control network manager (because the icon does not show up) counts as not being able to get a network connection, but that's not my decision. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, Aug 9, 2009 at 12:24 PM, Ralf Ertzinger wrote: > Hi. > > On Sun, 09 Aug 2009 12:11:58 -0700, Adam Williamson wrote > >> No, we wouldn't consider it blocking the Alpha per the criteria (we >> consider only bugs that break the critical path - booting into X, >> getting a network connection and updating the system - as blockers for >> the Alpha, pretty much). > > One may argue that being unable to control network manager (because the > icon does not show up) counts as not being able to get a network connection, > but that's not my decision. > Just until this gets fixed: I bring up the sound applet by running 'killall gnome-volume-control-applet; gnome-volume-control-applet&' from a terminal. Similarly, I can "recover" the NetworkManager applet by running 'killall nm-applet; nm-applet&', also from a terminal tom -- Tom London -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
Hi. On Sun, 9 Aug 2009 12:38:37 -0700, Tom London wrote > Similarly, I can "recover" the NetworkManager applet by running > 'killall nm-applet; nm-applet&', also from a terminal That used to work, these days it works better to restart NetworkManager itself. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: No sound in rawhide
On Sun, 2009-08-09 at 21:24 +0200, Ralf Ertzinger wrote: > Hi. > > On Sun, 09 Aug 2009 12:11:58 -0700, Adam Williamson wrote > > > No, we wouldn't consider it blocking the Alpha per the criteria (we > > consider only bugs that break the critical path - booting into X, > > getting a network connection and updating the system - as blockers for > > the Alpha, pretty much). > > One may argue that being unable to control network manager (because the > icon does not show up) counts as not being able to get a network connection, > but that's not my decision. That's a reasonable position (although there is a workaround). The blocker decisions are taken by releng plus qa plus anyone else who wants to show up. We have been announcing all the meetings here and encouraging people to come out and propose bugs which are not currently on the list :) The last blocker review meeting has passed already, but there is a final Alpha go/no-go meeting on Monday, you could certainly come and raise your concern there. My inkling is that we probably would not hold the Alpha solely for this issue (it doesn't appear it will be fixed until some time this week when the maintainer's back from vacation), but it's certainly worth asking. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
