display a mute icon until volume is changed since update

Bug #537977 reported by Sebastien Bacher
138
This bug affects 36 people
Affects Status Importance Assigned to Milestone
The Sound Menu
Fix Released
Undecided
Conor Curran
indicator-sound (Ubuntu)
Fix Released
Medium
Conor Curran
Lucid
Fix Released
Medium
Conor Curran

Bug Description

Binary package hint: indicator-sound

That started happened after the recent update, the volume is not muted and the slider is correct but the icon in the indicator bar is displayed as muted until volume is changed

indicator-sound-service log when starting the indicator and getting the issue

"** (process:6095): DEBUG: Root ID: 1
** (process:6095): DEBUG: update pa state with state 0, availability of 0, mute value of 0 and a volume percent is 0,000000
** (process:6095): DEBUG: Building new Slider Menu Item
** (process:6095): DEBUG: !!!!!!**in the rebuild sound menu - slider active = 0
** (process:6095): DEBUG: Emitting signal: SINK_AVAILABILITY_UPDATE, with value 0
** (process:6095): DEBUG: Emitting signal: SINK_VOLUME_UPDATE, with sink_volme 0,000000
** (process:6095): DEBUG: Emitting signal: SINK_MUTE_UPDATE, with sink mute 0
** (process:6095): DEBUG: connecting - waiting for the server to become available
** (process:6095): DEBUG: authorizing
** (process:6095): DEBUG: context setting name
** (process:6095): DEBUG: PA daemon is ready
** (process:6095): DEBUG: server info callback
** (process:6095): DEBUG: Just set the default sink index to 0

** (process:6095): WARNING **: Default Sink info callback failure
** (process:6095): DEBUG: About to add an item to our hash
** (process:6095): DEBUG: After adding an item to our hash
** (process:6095): DEBUG: About to test for to see if the available sink is null - s->name = alsa_output.pci-0000_00_1b.0.analog-stereo
** (process:6095): DEBUG: sink_available: 1
** (process:6095): DEBUG: software volume = 30,433655
** (process:6095): DEBUG: update pa state with state 1, availability of 1, mute value of 0 and a volume percent is 30,433655
** (process:6095): DEBUG: in the refresh menu method
** (process:6095): DEBUG: Emitting signal: SINK_AVAILABILITY_UPDATE, with value 1
** (process:6095): DEBUG: Emitting signal: SINK_VOLUME_UPDATE, with sink_volme 30,433655
** (process:6095): DEBUG: Emitting signal: SINK_MUTE_UPDATE, with sink mute 0
** (process:6095): DEBUG: Get sink volume method in the sound service dbus!, about to send over volume percent of 30,433655
** (process:6095): DEBUG: Get sink mute - sound service dbus!, about to send over mute_value of 0
** (process:6095): DEBUG: Get sink availability - sound service dbus!, about to send over availability_value of 1"

Related branches

Conor Curran (cjcurran)
Changed in indicator-sound (Ubuntu):
assignee: nobody → Conor Curran (cjcurran)
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Confirmed, it is strange, after a certain time, indicator-sound is displaying like the sound is muted, but it is not and can be verified by displaying notify-osd. Add a screenshot to it.

Changed in indicator-sound (Ubuntu):
status: New → Confirmed
Omer Akram (om26er)
Changed in indicator-sound (Ubuntu):
importance: Undecided → High
importance: High → Medium
Revision history for this message
Ryan (ryan-farmer-personal-deactivatedaccount) wrote :

This affects me too.

Changed in indicator-sound:
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

bug #538923 is similar with the status icon, libdbusmenu issue?

Revision history for this message
Ryan (ryan-farmer-personal-deactivatedaccount) wrote :

Seems if you remove the indicator-messages part of the indicator crapplet, the volume control part of the crapplet stops doing this.

Oh well, the messages part is part of the indicator crapplet fluff that pollutes the panel and destroys the user's sanity anyway. :)

Revision history for this message
Sebastien Bacher (seb128) wrote :

The previous comment doesn't respect the code of conduct and is out of order there

Omer Akram (om26er)
Changed in indicator-sound (Ubuntu Lucid):
status: Confirmed → Triaged
Revision history for this message
Ryan (ryan-farmer-personal-deactivatedaccount) wrote :

Well snap. It's perfectly obvious that if you didn't remove the volume applet that's supposed to be there anyway, this wouldn't be happening.

Revision history for this message
Rafael Belmonte (eaglescreen) wrote :

The same here, in Lucid upgraded from karmic.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-sound - 0.1.3.1-0ubuntu2

---------------
indicator-sound (0.1.3.1-0ubuntu2) lucid; urgency=low

  * Backport upstream changes to fix those issues:
    - "Wrong i18n for menu entries", thank Luca Ferretti (lp: #538704)
    - "display a mute icon until volume is changed since update" (lp: #537977)
 -- Sebastien Bacher <email address hidden> Mon, 15 Mar 2010 15:51:35 +0100

Changed in indicator-sound (Ubuntu Lucid):
status: Triaged → Fix Released
Revision history for this message
Sam Townsend (stownsend42) wrote :

I still see this problem even with the latest update.

Revision history for this message
Omer Akram (om26er) wrote :

Sam, its fixed in indicator-sound 0.1.3.1-0ubuntu2 please do 'apt-cache policy indicator-sound' to check which version you have.

Revision history for this message
Sam Townsend (stownsend42) wrote :

Disregard my last message. The problem disappeared after a reboot.

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :

I seem to still experience this, despite having installed the latest updates. Perhaps my mirror (za.archive) is slow to get the latest packages?

Revision history for this message
Conor Curran (cjcurran) wrote :

Hi Eduard,

Which version do you have installed ?
apt-cache policy indicator-sound - could you check paste in the output of the above command here

Changed in indicator-sound:
milestone: none → 0.1.3.1
assignee: nobody → Conor Curran (cjcurran)
Conor Curran (cjcurran)
Changed in indicator-sound:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.