[Intrepid, Jaunty, Karmic] After pressing a multimedia key (volume), keyboard no longer reponds

[Steffen Rusitschka]

Binary package hint: xserver-xorg-input-kbd

When pressing any of the two volume multimedia keys, the key press repeats itself forever. E.g. the volume goes up to max. when pressing the corresponding key. It stops when pressing CR but afterwards every keyboard input gets ignored. Only "Ctrl-Alt-Backspace" helps, i.e. kill X...
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: Inventec Corporation Device [1170:0040]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8600M GT [10de:0407] (rev a1)
     Subsystem: Inventec Corporation Device [1170:0040]

[Steffen Rusitschka (rusi)]

Any news on this one? It's pretty annoying since touching those keys by accident happens pretty often ...

(Oh and how can I fix the typo in the subject?)

[Romano Giannetti (romano-giannetti)]

A very similar thing happens to me with the volume wheel. Using showkeys in the console reports:

keycode 115 release
keycode 115 press
keycode 115 release
keycode 115 press
keycode 115 release
keycode 115 press
keycode 114 release
keycode 114 press
keycode 114 release
keycode 114 press
keycode 114 release
keycode 114 press

i.e., the wheel send release events *before* press events. The only workaround is to switch to a VC and then back to X. Can anyone suggest a way to disable the darn wheel before I open the laptop and get rid of it?

This bug could be a duplicate of bug#20681, only that one if marked as fixed and that's not true for me on Intrepid Ibex.

[Romano Giannetti (romano-giannetti)]

Maybe it is related to http://bugzilla.kernel.org/show_bug.cgi?id=10300

[Romano Giannetti (romano-giannetti)]

To rusi: you don't need to kill X. Just switch to a text VC (i.e., ctrl-alt-f1 a couple of times) and then back to X (alt-f7 or alt-f8 or alt-f9) and keyboard will be ok again.

[Romano Giannetti (romano-giannetti)]

Another point: please notice that this is, for me, a Intrepid regression. Touching the wheel in hardy simply gave random results on the volume, but no keyboard lock. Now I need the VC switch trick. Not funny.

[Bryce Harrington (bryce)]

Hi rusi,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Steffen Rusitschka (rusi)]

lspci -vvnn

[Steffen Rusitschka (rusi)]

xorg.log

[Steffen Rusitschka (rusi)]

My xorg.conf is basically "empty":

Section "Device"
        Identifier "Configured Video Device"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

[Romano Giannetti (romano-giannetti)]

I am not rusi but I will add the same info...

[Romano Giannetti (romano-giannetti)]

This bug is still here and still marked as "incomplete". Please tell me what you need to complete it (still present and still very nasty).

[Bryce Harrington (bryce)]

I think this is probably not a -keyboard bug but rather either a kernel or hal-info issue. Forwarding to hal-info for further troubleshooting. There have been a number of improvements with hotkey handling in Jaunty, would you mind retesting against that?

[Taner Senyurt (turshu)]

Solution Exist Here : http://www.tsenyurt.com/?p=56

[Martin Pitt (pitti)]

This sounds similar to the problems that we had on Samsung NC10 and NC20. Do you still have the issue in Jaunty?

[Romano Giannetti (romano-giannetti)]

Cannot upgrade to Jaunty, due to X and suspend/resume being broken for me (see bug#339091)

[kernel-janitor (kernel-janitor)]

Hi Steffen,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p alsa-base 273745

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Romano Giannetti (romano-giannetti)]

Still here in Karmic. I do not think that doing the "apport" trick is useful, I think this is a keyboard, X or kernel glitch.
This is really a "paper-cut" of enormous proportion, especially given that there is a solution (the one cited above,
http://www.tsenyurt.com/2009/03/29/ubuntu-volume-wheel-problem-fix/ ).
Will try to see if I can adapt this to karmic.
I do not think that the tagging as "incomplete" is right.

[Romano Giannetti (romano-giannetti)]

Souldn't this bug be assigned to the "evdev" project? i am trying to change the project but couldn't find how.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.