Comment 22 for bug 237604

Revision history for this message
Huandari Lopez (outofreach137) wrote :

I am also experiencing this bug. And weirdly enough, I didn't have this problem before.
I'm not quite sure what the problem is, I am using KDE, and the only thing that I have done that seems peculiar is manually compiling and installing Firefox 3.5, but this bug does not only happen in Firefox.

I find that pressing (or rather, smashing) on the ctrl or shift keys fixes the problem..for the while. I have switched keyboards and yet the problem occures. I do have this in my dmesg:
[ 276.254455] atkbd.c: Unknown key released (translated set 2, code 0x9f on isa0060/serio0).
[ 276.254457] atkbd.c: Use 'setkeycodes e01f <keycode>' to make it known.
[ 1035.775827] atkbd.c: Unknown key pressed (translated set 2, code 0xac on isa0060/serio0).
[ 1035.775829] atkbd.c: Use 'setkeycodes e02c <keycode>' to make it known.
[ 1036.153698] atkbd.c: Unknown key released (translated set 2, code 0xac on isa0060/serio0).
[ 1036.153699] atkbd.c: Use 'setkeycodes e02c <keycode>' to make it known.
[ 1036.518231] atkbd.c: Unknown key pressed (translated set 2, code 0xac on isa0060/serio0).
[ 1036.518232] atkbd.c: Use 'setkeycodes e02c <keycode>' to make it known.
[ 1036.771764] atkbd.c: Unknown key released (translated set 2, code 0xac on isa0060/serio0).
[ 1036.771765] atkbd.c: Use 'setkeycodes e02c <keycode>' to make it known.
And many more of those. Again, this only just recently began happening.