Perfectly normal (but old) keyboard dysfunctional on a VT (Breezy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hotkey-setup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This bug is related to the keyboard-setup in linux, filing under "hotkey-setup" (due to reasons explained later), unsure in what way this is related to "console-data".
EDIT: I thought I filed this under "hotkey-setup" already at first, but apparently this was not registered. I have now changed the report to refer to the binary package "hotkey-setup".
In a virtual terminal, when pressing (e.g.) LeftShift-PageUp (or LeftShift-PageDown, LeftShift + any arrow key) to scroll up, I get an error message on the following lines:
"atkbd.c: Unknown key pressed (translated set 2, code 0xaa on isa0060/serio0).
atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known."
When I set NumLock on, this particular issue disappears, but PgUp, PgDn, all arrow keys on their own generate identical error messages.
I have a trusty old Finnish 102-key keyboard (not even a Win-key) that has worked for me on every system I've used (DOS, Win 3.11, Slackware...), except, sadly, on Kubuntu.
Now, the bug _seems to be_ hotkey-setup related. A search on ubuntuforums.org with the terms "setkeycodes e02a" throws up a profusion of topics (most of which just contain dmesg output pasted to solve other, unrelated problems), in which several solutions are suggested. Among the solutions suggested are re-assigning the keycode e02a in /usr/share/
EDITed: Stopping hotkey-setup seems to work for me (at least I have yet to found any negative effects due to that). However, as keyboard functionality is such a basic issue, I do hope that this issue can be addressed for people to be able to use their regular, "no extra-keys" -keyboards.
EDIT: I have recently noticed, after filing this report, that Ubuntu-bugzilla 17569 claims that this issue is fixed (in a version of hotkey-setup not released for Breezy, so I am not able to test, thus I think filing this report was necessary).
Besides, it is unexpected that Shift-UpArrow and Shift-DownArrow do _not_ scroll the display buffer one line at a time. Is this an expected behaviour in Ubuntu, or should I file a separate report on that (against "console-data"), or will it best be handled in conjunction with this report?
Now, is it possible that this could in some way be fixed (in Breezy), if I were to supply you with any information that you need?
In case it's of any use, as I noticed that "/etc/init. d/hotkey- setup" uses dmidecode.