Comment 0 for bug 41834

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".

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/hotkey-setup/generic.hk, or removing the keycode from there, or simply stopping hotkey-setup.

<rant>Stopping hotkey-setup seems to work for me (at least I have yet to found any negative effects due to that), but I really wouldn't have expected that I would need to battle with such a basic issue as keyboard functionality. I believe that I can appreciate the difficulty in trying to support all manner of different laptop & special keyboard extra-key combinations - well, maybe not - but _is it really necessary that a perfectly regular, "no extra-keys" -keyboard becomes dysfunctional in the process_ ? </rant> Sorry about the rant.

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?