GNOME Bugzilla – Bug 478498
[alsamixer] Scale gets out of sync with hardware levels
Last modified: 2011-08-11 12:49:37 UTC
+++ This bug was initially created as a clone of Bug #478485 +++ Using the attached patch, which logs get/set on the volume, I can see that log: ** Message: set: volume 0• ** Message: get: volume 0.000000 (scale 0.000000) mute 0 1• ** Message: get: volume 0.000000 (scale 0.000000) mute 0 1• ** Message: set: volume 11• ** Message: set: volume 31• ** Message: get: volume 0.000000 (scale 100.000000) mute 0 1• ** Message: get: volume 0.000000 (scale 100.000000) mute 0 1• (31 is the upper level of my master track mixer) This means that the "set 11" and "set 31" failed (GstAlsa has _no_ error checking whatsoever). The mixer API doesn't allow for failure. Some calls to ALSA might fail, and the volume isn't set or retrieved properly, which means that the applet's state goes completely bonkers when changing the volume quickly (I mean really quickly).
Upstream report: https://bugs.launchpad.net/gnome-applets/+bug/136837
(In reply to comment #1) > Upstream report: https://bugs.launchpad.net/gnome-applets/+bug/136837 That's downstream, we're upstream (unless Ubuntu have chosen to start maintaining gnome-applets :) FYI, the patch above fixed it for Fedora users too: https://bugzilla.redhat.com/show_bug.cgi?id=295311
Whoops, I get confused sometimes. Launchpad and GNOME Bugzilla look the same these days. :P
Can we merge the Fedora patch?
Can someone who actually knows where the patch is attach it?
Bug 478512 is very similar to this one.
(In reply to comment #5) > Can someone who actually knows where the patch is attach it? There's no patch, the patch mentioned is for gnome-applets and lives in bug 478485, this is the actual bug report part: " The mixer API doesn't allow for failure. Some calls to ALSA might fail, and the volume isn't set or retrieved properly, which means that the applet's state goes completely bonkers when changing the volume quickly (I mean really quickly). "
*** Bug 509592 has been marked as a duplicate of this bug. ***
*** Bug 557333 has been marked as a duplicate of this bug. ***
Is there still something to fix here?
any news for this?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!