After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557333 - gsd-media-keys-manager sometimes shows zero volume when it shouldn't
gsd-media-keys-manager sometimes shows zero volume when it shouldn't
Status: RESOLVED DUPLICATE of bug 478498
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.24.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2008-10-21 22:50 UTC by Bogdan Butnaru
Modified: 2008-10-22 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Bogdan Butnaru 2008-10-21 22:50:08 UTC
Hi!

I'm using gnome-settings-daemon from the Ubuntu repositories, version 2.24.0-0ubuntu3 (which is pretty much the same as the normal 2.24 one). And I'm getting a very weird bug:

Sometimes when I change the volume using my laptop's volume keys the gsd-media-keys-window shows the volume as 0. However it's clearly not zero, as the sound continues normally at the correct volume.

I've hacked some printf's into the sources to try to figure out what's going on but without much success. The only thing I've seen from my logs is that acme_volume_gstreamer_set_volume is called, it seems to do everything successfully, but next time acme_volume_gstreamer_get_volume gets called it calls update_state, which calculates a zero volume.

The more precisely I try to corner the issue with printf's the harder it is to reproduce. (I just turn the volume all the way up and down; without printfs it happens at least once per cycle, with more it happens tens of times less often.) It seems there's a kind of race there, which is weird because as far as I can tell there's a single thread involved...

I've seen this reported on Ubuntu forums, so I'm not the only one seeing it. I don't really know how to investigate further, maybe someone could guide me?
Comment 1 Jens Granseuer 2008-10-22 16:41:21 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 478498 ***