Mute conflict between gnome-volume-applet and gnome-volume-manager

This happens for me too. The only way to "unmute" it again for me is to use my volume up/down from my keyboard and this restores the volume. However... I'm also experiencing another "symptom" -- but not sure if I should file it as a separate bug or not. On my system, with an onboard VIA 8235 (Alsa) AC97 chipset, even when I have the volume slider(s) all the way down and it claims to be "muted," I still receive sound at a very low volume through my speakers. It's not until I actually choose to mute it that the sound stops.

To ensure that both issues are fixed, it is probably better to open a new bug for the low volume sound issue. Please also include the output of `lspci | grep audio` in the report, as it doesn't happen on my system.

Using the latest Dapper, I can confirm this bug. The same happens to me. I can another inconsistency.

1) Using mute button on my laptop IBM r50e I can easily mute sound. The applet as well as the Volume Control show the correct stat (mute).

2) Now, if I want it to unmute, I can do it only by the laptop volume up button. Neither unmuting by the applet, by the laptop mute button nor by the Volume Control helps. It seems that they work (mute icon disappears) but I cannot hear any sound.

In my opinion, this should be corrected so that all the applet mute, the Volume Control mute and the laptop mute key unmute the sound.

The keybinding mute issue should probably also have a separate bug. On my workstation, the keybindings control the Master volume, and the applet slider controls the PCM volume. When using the keybindings, all operations are correct, whether Volume Control is open or not, and apply to the Master volume. PCM is unaffected, and the applet correctly displays no change based on the adjustments.

For those finding this bug when having an issue other than the irregular muting when using the volume control applet slider with the Volume Control panel open, please keep searching. You may be experiencing Bug #42240, or perhaps even a different issue, which should also be reported.

Thanks for your bug. There is several upstream bugs around that topic:
http://bugzilla.gnome.org/show_bug.cgi?id=319139
http://bugzilla.gnome.org/show_bug.cgi?id=333438
http://bugzilla.gnome.org/show_bug.cgi?id=331764

I've forwarded it upstream pointing the other bugs, they will decide if that's a duplicate of one of those: http://bugzilla.gnome.org/show_bug.cgi?id=341021

fixed upstream, thanks for reporting.

the new version is in intrepid now

why did you open a debian bug there? closing it