volume changes work correctly but the OSD always shows full volume and "plips" at the same level

Bug #840971 reported by Andy Whitcroft
68
This bug affects 12 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Unknown
High
The Sound Menu
Invalid
Medium
Conor Curran
gnome-settings-daemon (Ubuntu)
Triaged
Medium
Mirco Müller
indicator-sound (Ubuntu)
Invalid
Medium
Conor Curran

Bug Description

The volume controls on this machine work fine, but the visual feedback OSD display always shows the highest value and "plips" at the same highest volume indication.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: indicator-sound 0.7.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sun Sep 4 13:42:07 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to oneiric on 2011-08-05 (29 days ago)

Revision history for this message
Andy Whitcroft (apw) wrote :
Changed in indicator-sound (Ubuntu):
status: New → Confirmed
Conor Curran (cjcurran)
Changed in indicator-sound:
assignee: nobody → Conor Curran (cjcurran)
Conor Curran (cjcurran)
Changed in indicator-sound:
status: New → Confirmed
Revision history for this message
Omer Akram (om26er) wrote :

this only happens when the volume is changed with keyboard controls.

Omer Akram (om26er)
Changed in indicator-sound:
importance: Undecided → Medium
Changed in indicator-sound (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Mirco Müller (macslow) wrote :

After pulling the latest updates, I get this behaviour also. NotifyOSD did not change and only displays what it gets send from another process. So the process sending out the notification is passing something wrong. If in doubt see the examples notify-osd/examples/icon-value.c (or icon-value.py) for a demonstration how to correctly use the current libnotify-API.

Earlier in this cycle I've see libnotify behaving differently for passing hints to notifications. Be sure to always set values for any hint you send. This could be a cause for the wrong display of the volume.

Revision history for this message
Mirco Müller (macslow) wrote :

Additional tip... with the newer version of libnotify I had to update all examples/tests of notify-osd with regards to passing hints to notifications. For example the value of a boolean hint should not be left empty. So is should read...

notify_notification_set_hint_string(notification, "x-canonical-private-synchronous", "true");

It used to be...

notify_notification_set_hint_string(notification, "x-canonical-private-synchronous", "");

which causes similar issues.

Revision history for this message
Mirco Müller (macslow) wrote :

Doh... meant string-hint, not boolean-hint.

Conor Curran (cjcurran)
Changed in indicator-sound:
status: Confirmed → Invalid
Changed in indicator-sound (Ubuntu):
status: Confirmed → Invalid
Changed in gnome-settings-daemon:
status: New → Invalid
importance: Undecided → Unknown
status: Invalid → Unknown
Revision history for this message
Conor Curran (cjcurran) wrote :

Volume keys are handled by G-S-D, reassigning.

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

Apparently the problem is one of our own distro patches.

Mirco Müller (macslow)
Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Mirco Müller (macslow)
importance: Undecided → Medium
status: New → Confirmed
milestone: none → ubuntu-11.10-beta-2
Changed in gnome-settings-daemon:
importance: Unknown → High
Revision history for this message
Michael Moorman (tensorpuddin) wrote :

I am experiencing what is probably the same problem, except that it always shows as if it was muted, instead of at full volume.

Dave Walker (davewalker)
Changed in gnome-settings-daemon (Ubuntu):
milestone: ubuntu-11.10-beta-2 → ubuntu-11.10
Revision history for this message
Michael Moorman (tensorpuddin) wrote :

After installing the latest round of updates, the problem has gone away.

Revision history for this message
Séverin Lemaignan (skadge) wrote :

I confirm the issue has been fixed for me too.

Changed in gnome-settings-daemon (Ubuntu):
status: Confirmed → Triaged
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.