indicator-sound-service interferes with gnome-settings-daemon

[Chris Coulson]

This has been bugging me for weeks now, so I decided to take a look at it today.

To reproduce the bug, do the following:
1) Ensure that the current volume is less than one step above 0.
2) Press the volume down media-key on your keyboard
3) Observe that the volume notification shows zero volume and a muted icon, but the sound indicator shows zero volume and unmuted
4) Press the volume down media-key again
5) Observe that the volume notification shows the same notification again, and the sound indicator also now shows the sound as muted.
5) Press the volume down media-key again
6) Observe that the volume notification shows muted with the throbbing effect.

What *should* have happened is that at 3, the sound indicator should also have shown muted. At 5, the volume notification should have been with the throbbing effect.

What happens is:

At 2, gnome-settings-daemon sets the volume to zero and mutes the output. It then displays this state in the notification on the screen. However, according to Pulseaudio, indicator-sound-service responds by also setting the volume to zero and unmuting the sound. So, at 4, gnome-settings-daemon mutes the sound *again*, but doesn't change the volume (as it's already zero), and indicator-sound-service doesn't unmute it this time.

I tried running without indicator-sound-service, and gnome-settings-daemon works correctly.

Note, this is what pulseaudio says at step 2:

D: [pulseaudio] protocol-native.c: Client gnome-settings-daemon changes volume of sink alsa_output.pci-0000_00_1b.0.analog-stereo.
D: [alsa-sink] sink.c: Volume change to 3932 at 8118661020 was written 3384381 usec late
D: [alsa-sink] alsa-sink.c: Requested volume: 0: 0% 1: 0%
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 0% 1: 0%
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 0% 1: 0% (accurate-enough=no)
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] sink.c: Volume going down to 0 at 8122037545
D: [alsa-sink] sink.c: Volume change to 0 at 8122037545 was written 8008 usec late
D: [alsa-sink] alsa-sink.c: Written HW volume did not match with the request: 0: 0% 1: 0% (request) != 0: 0% 1: 0%
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB (request) != 0: -inf dB 1: -inf dB
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1b.0.analog-stereo:analog-output.
D: [pulseaudio] protocol-native.c: Client gnome-settings-daemon changes mute of sink alsa_output.pci-0000_00_1b.0.analog-stereo.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1b.0.analog-stereo:analog-output.
D: [pulseaudio] protocol-native.c: Client indicator-sound-service changes volume of sink alsa_output.pci-0000_00_1b.0.analog-stereo.
D: [alsa-sink] alsa-sink.c: Requested volume: 0: 0% 1: 0%
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 0% 1: 0%
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 0% 1: 0% (accurate-enough=no)
D: [alsa-sink] alsa-sink.c: in dB: 0: -inf dB 1: -inf dB
D: [alsa-sink] sink.c: Volume not changing
D: [pulseaudio] protocol-native.c: Client indicator-sound-service changes mute of sink alsa_output.usb-Logitech_Logitech_USB_Headset-00-Headset.analog-stereo.
D: [pulseaudio] protocol-native.c: Client indicator-sound-service changes mute of sink alsa_output.pci-0000_00_1b.0.analog-stereo.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1b.0.analog-stereo:analog-output.
I: [pulseaudio] module-device-restore.c: Synced.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Conor Curran (cjcurran)]

Very weird, looking into this now.

I find it funny that people consider this to be a high priority when as it stands now the unmute button is broken when the volume is at 0.

[Conor Curran (cjcurran)]

And the gnome sound preferences open at the same time.

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-sound - 0.7.8-0ubuntu1

---------------
indicator-sound (0.7.8-0ubuntu1) oneiric; urgency=low

  * New upstream release.
    - indicator-sound interferes with gnome-settings-daemon (LP: #855557)
  * debian/patches/01_fix_FTBFS.patch
    - Dropped, fixed upstream
 -- Ken VanDine <email address hidden> Wed, 28 Sep 2011 14:34:38 -0400