GNOME Bugzilla – Bug 418510
Sound is displayed as mute after suspend/resume whereas it is not
Last modified: 2007-03-15 15:39:47 UTC
Please describe the problem: Bug was reported on Ubuntu launchpad: https://launchpad.net/ubuntu/+source/gnome-applets/+bug/90341 This apply more specifically to the Gnome Volume Control applet that is displayed by default near the date&time in the top bar of the Gnome Desktop. The version of this applet is 2.18.0. The problem is minor and cosmetic only. It occurs after the following sequence of event: suspend & resume. After, resume the session is locked, when I unlock it using my user password, I get the desktop back. The volume applet shows the sound as muted (whereas it was not in this state before suspend). However, it is not muted, I can hear sounds. To come back to normal is pretty easy. A press on the mute sound special key of my keyboard and the sound is now really muted (the display stay unchanged). A second pressure on the same key brings back the sound to not muted and the display is then correct. This bug is reported after the test performed on Dell Latitude D600 (cf. https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD600) Steps to reproduce: 1. Set the sound on (not displayed as mute) 2. Suspend (a.k.a. sleep) 3. Resume Actual results: The sound is displayed as mute, but you could listen to music so it is not mute. Also, before the suspend/resume the sound was not mute. Expected results: That the sound is not displayed mute (display problem) Does this happen every time? Yes Other information: Bug tested on Ubuntu Feisty Fawn on a Dell Latitude D600 laptop. The workaround is simple: 1. press the mute button (-> the sound is display again as mute, but this time it is really mute) 2. press the mute button again (-> the sound is no longer displayed as mute and music can be heard again) N.B.: I have a special key on my keyboard to mute the sound.
I am sorry for having open this bug. But it seems to have been obsolete by a recent update on Ubuntu Feisty Fawn. I have tried to reproduce it today, and I cannot. My initial report in Launchpad was on the version 2.17.90 of the gnome-applet, it seems that some change in 2.18.0 has occurred and corrected the problem. I have marked the bug as fixed, feel free to correct my statement as I'm not really familiar with Gnome or Bugzilla bug status convention. I'm going to close now the bug report on Launchpad too. Sorry for any inconvenience.