Red Hat Bugzilla – Bug 127220
Gnome does not remember volume levels and applet can't hold volume level
Last modified: 2007-11-30 17:10:45 EST
Description of problem:
Front left and right channels turned off everytime I log into X.
Gnome Volume Applet beside clock automatically lowers when raised
Version-Release number of selected component (if applicable):
From Fedora Core 2
On desktop with SoundBlaster Live 5.1, every time I log into X.
Steps to Reproduce:
1. Log into X
2. Raise Master volume from 0 to X (on gnome volume control panel)
3. Log out of X
4. Log into X, volume is 0 again
1(a). Log into X, raise volume on applet
Volume stays at proper that level if I do not log out of X. For
applet, it slowly lowers until 0.
Volume is always remembered on front channels. For applet, it should
stay where I leave it.
Rear channels do not change levels. (not on IBM A22M with crystal
sound laptop). I tried to use the save desktop preferences by
checking the box when logging out of X, but it does not fix the sound
There's a similar problem in Development - volume level aren't saved
so they default to zero.
It's a highly annoying bug as a user, because you have to turn up the
volume with each reboot.
This problem solved itself for me when I tried to install a
SoundBlaster Audigy LS. Since it is unsupported in FC2, I put my SB
live 5.1 back in and now my sound is remembered. I wonder why this
didn't work properly from inital install.
This is an alsa-level issue.
*** This bug has been marked as a duplicate of 119866 ***
*** Bug 82709 has been marked as a duplicate of this bug. ***
*** Bug 83468 has been marked as a duplicate of this bug. ***
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.