5:15 p.m.
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..
miketc302(a)fedoraproject.org
5:20 p.m.
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
2:13 a.m.
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
8:19 a.m.
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..
miketc302(a)fedoraproject.org
9:47 a.m.
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 -vvvvv') and file a bug.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12:51 p.m.
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?
2:11 p.m.
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
2:13 p.m.
On Sun, Aug 9, 2009 at 9:11 PM, Adam Williamson<awilliam(a)redhat.com> 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
2:24 p.m.
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.
2:38 p.m.
On Sun, Aug 9, 2009 at 12:24 PM, Ralf Ertzinger<fedora(a)camperquake.de> 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
3:13 p.m.
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
5431
days inactive
5432
days old
11 comments
6 participants
participants (6)
-
Adam Williamson -
drago01 -
Mike Chambers -
Ralf Ertzinger -
Tom Callaway -
Tom London