GNOME Bugzilla – Bug 156330
Volume Up,Down,Mute keyboard shortcuts have no effect
Last modified: 2009-08-15 18:40:50 UTC
I used the Keyboard Shortcuts capplet to assign keys to Volume mute, up, and down. Pushing the respective key causes a pop-up window to appear with a speaker icon and an empty bar The bar should fill-up as I repeated push the volume up key, but there is no change to the bar or the volume.
I'm encountering the same problem. However, after I recompiled control-center with --disable-gstreamer option, the mute button seems to be working, volume up/down are still the same as before(a window appears, but the volume doesn't change, nor does the bar on the window). My system uses alsa-1.0.6, with two soundcards enabled(soundblaster audigy2, intel i8x0). Linux distribution is gentoo. Kernel version is 2.6.9-gentoo-r1. Control-center version is 2.8.0.
I get the same problem with GNOME 2.6.2 and kernel 2.6.9 (vanilla) on Gentoo. The problem also occurred with kernel 2.6.7, which is why I broke out the kernel upgrade. Does anyone happen to know the program or source file that gets called when you press the volume buttons? This has me so annoyed I'm actually willing to go through the source to try and fix it myself. I just have no clue where to start looking (GNOME is big. Real big. Huge even.)
I have this as well on Gentoo, linux-2.6.7-gentoo-r7, gnome 2.8. There has been an evolution in this deteriorating OSD applet. Since some version in gnome 2.6 it started to be displayed at two different positions on the screen. And now, with gnome 2.8, it doesn't change at all anymore. Cheers pjv
after upgrading from 2.6 to 2.8, the buttons seem to be working with my intel sound card(I have two sound cards configured, SB audigy with index=0, intel i8x0 with index=1, I use my intel i8x0 for front panel headsets), my audigy card is still the same as before. this time I have to compile with gstreamer, disabling it will make the buttons unfunctional again. I really hope this gets fixed soon.
Moving to the right component. Key question: what kind of HW are you using the keyboard on? On IBM laptops, for example, this requires extra drivers, I believe, to work correctly.
No special hardware. This is a generic desktop computer with an Athlon "Thunderbird" CPU and VIA motherboard. However, I am using an ATI Remote Wonder remote control which emits X11 keyboard events. I upgraded to Gnome 2.8.1 and the volume control seems to work. However, the window which pops up to display the volume level when I push volume up/down stays on the screen until I click somewhere else with my mouse to make it lose focus.
I'm using ViewSonic Slim Keyboard KU201, it's a USB keyboard. I can capture the keycodes no problem with xev, and the keys work fine when I used hotkeys, so I dont think it's a driver problem.
Using Fedora Core 3 updated to today's date I have the same problem. It seems to involve two things: - My ALSA drivers for the hw (snd_via82xx) are configured so that the "Master Volume" channel does not affect the sound at all. ("Master Surround" and "PCM" does, though). Using gnome-alsamixer I've discovered that the shortcuts does indeed affect the "Master Volume" to no use. - The Mute keyboard function does *not* mute the channel, it just decreases the volume to 0. As a result, it cannot be restored is is not totally silent. My workaround has been the xhkeys package. It works, but feels clumsy and takes some time to configure. RFE: A configuration option to select the channel to handle with the volume shortcuts, like the volume control applet already have (Also ACME had such an option). The channel used by the volume control is probably a reasonable default value, but might be wrong e. g., for users who want to handle headphones volume with the shortcuts. To really mute/unmute instead of decreasing the volume must be considered a bugfix IMHO.
My version: control-center-2.8.0-12
In the latest build the pop-up window appears with a speaker icon and an empty bar. The bar filled-up as I repeated pressing the volume-up key. test@linux:~> gnome-keybinding-properties --version Gnome gnome-keybinding-properties 2.9.5 test@linux:~> gnome-control-center --version Gnome gnome-control-center 2.9.5
shakti : The problems are going to be system dependent. For example some alsa systems use PCM & Headphones to contol the volue rather than Master.
I just had the same (annoying) problem and looke into it a bit. The real bug seems to be that the shorcuts don't "guess" the device and channel to modify correctly. On my machine a temporary fix was to do echo VOLUME "PCM" 0 > /proc/asound/card0/oss_mixer which means that the shortcuts on my machine were actually controlling the fake oss mixer alsa provides, even though I have set all preferences (that I found namely: volume applet, volume manager and in "Sound") to control ALSA. Also all this preferences don't affect each other, so there doesn't seem to be any global place to configure the default device for all volume control applications, so the Shortcut Dialog doesn't seem to have any place where it could get the information which device to control and which channel. The misteryous part (to me) is: Where does it get it's configuration right now, or is it actually guessing?
Seems to be fixed with me since a long time, just with some gnome update probably. But I think the last commenter is searching in the right direction. See also: http://bugs.gentoo.org/show_bug.cgi?id=72796
Enhancement Bug #173035 is a duplicate of this bug. Or worded differently, it addresses the same problem namely the controlling of the wrong channel.
Let's dup it then, there's some ongoing work in that bug report to fix this issue. *** This bug has been marked as a duplicate of 173035 ***