From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
After installing Fedora Core 2 on an IBM Thinkpad 600X, type 2645-5EU,
the sound controller was properly detected. Upon logging into gnome,
the volume for all channels was set to zero, as expected. The main
problem I am having is that setting the volume of the Master channel
(the Alsa Master channel) using the panel applet does not work. If I
single left click on the applet to get the volume slider and set a
volume, the setting has no effect on currently playing audio, and the
volume creeps back down to zero. If I open the Volume Control app and
set the volume on the Master channel in the Alsa tab, that works, and
the volume stays where I set it. Likewise with the corresponding OSS
channel, called Volume instead of Master.
Opening up the "Volume Control" application (gnome-volume-control)
from the mixer panel applet, I see there are two modules I can
control: "Sound Fusion CS46xx [Alsa Mixer]" and "Cirrus Logic CS4297A
rev 3 [Audio Mixer (OSS)]." The Alsa tab has 41 channels to control.
The OSS tab has 13, all of which appear in the Alsa tab. Changes to
these common channels do not appear to be reflected across tabs (set
PCM to a certain level in OSS, and the PCM channel does not show the
same change in Alsa, but changes made to PCM in either tab take
immediate effect, so no big deal there).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Assuming a right-naded mouse configuration, single left click on
the volume control applet to get volume slider
2. Set volume to any nonzero setting
Actual Results: Volume set in step 2 is never effected, and volume
creeps down to zero by itself
Expected Results: Setting should take effect and stay at specified level
I see exactly the same bug on ThinkPad T20
This is a duplicate of bug 121376, which in turn is a duplicate of the
upstream http://bugzilla.gnome.org/show_bug.cgi?id=139961, which is
fixed in gnome-applets-2.6.1. I have links to some updated rpms that
work for me in bug 121376.
Thanks Elijah, the 2.6.1 RPM on that site fixed things for me too.
*** This bug has been marked as a duplicate of 121376 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.