Invalid keycode spam in dmesg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
Fix Released
|
Medium
|
Mantas Kriaučiūnas | ||
hotkey-setup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
My dmesg quickly fills up with messages like this:
[4300347.514000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4300347.514000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
knocking any useful information out of the buffer. This keycode seems to be my
up arrow key, which of course I use a lot in the shell. Apparently there's some
worry that it'll trigger a hibernate on some laptops, but I don't think this is
the case. I originally suspected it was because I was on a laptop but using a
regular AT keyboard through a docking station, but I get the same behavior on
desktop machines and have acquired anecdotal evidence that it's pretty universal.
If I remove the line about e02a from /usr/share/
/etc/init.
be removed from generic.hk in the hotkey-setup package.
Created an attachment (id=5338)
Removes e02a keycode from generic.hk