GNOME Bugzilla – Bug 140937
Inconsistancies using keybindings to control volume
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: Volume control using keybindings (formerly acme) seems to be inconsistant. (Note: I am using alsa and udev, if either make a difference). It seems that the code formerly known as acme stores its own volume state, and does not check the current level of the mixer. If between key usage I adjust the volume in another way, say the gnome panel applet, and go back to the keys, it does not adjust the volume up from the actual volume, but from the last volume set by the key.. adjusting in a higher or lower starting point that you were expecting.
This may be worthy of its own bug, but it also appears that the keybinding action Mute, rather than effectively muting and restoring to the previous volume level does nothing more than set the volume to 0.. this does not toggle back as the mute action in the gnome volume applet does.
This bug is now fixed in CVS. 2004-07-15 Bastien Nocera <hadess@hadess.net> * actions/acme-volume-alsa.c: (acme_volume_alsa_finalize), (acme_volume_alsa_set_mute), (acme_volume_alsa_get_mute), (acme_volume_alsa_get_volume), (acme_volume_alsa_set_volume), (acme_volume_alsa_close_real), (acme_volume_alsa_open), (acme_volume_alsa_close), (acme_volume_alsa_init): rework the ALSA mixer so that: - the ALSA device isn't kept open at all times, only for 4 seconds after the last use (Closes: #141793) - the hardware mute is used if it is available (Closes: #141404, #144489, #140937) - lowering the volume doesn't move the balance to the right - it doesn't leak alsa-lib mixers all around