| 2006-04-28 07:15:15 |
kko |
bug |
|
|
added bug |
| 2006-04-28 07:23:59 |
kko |
bug |
|
|
added attachment 'keyboard_bug_dmidecode-output.txt.gz' (Output of "sudo dmidecode") |
| 2006-04-28 07:34:51 |
kko |
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".
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? |
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.
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).
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? |
|
| 2006-04-28 07:34:51 |
kko |
title |
Perfectly normal (but old) keyboard dysfunctional on a VT |
Perfectly normal (but old) keyboard dysfunctional on a VT (Breezy) |
|
| 2006-04-28 07:43:47 |
kko |
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".
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.
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).
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? |
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.
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? |
|
| 2006-04-28 07:47:55 |
kko |
None: status |
Unconfirmed |
Confirmed |
|
| 2006-04-28 07:47:55 |
kko |
None: statusexplanation |
|
Marking as confirmed (for Breezy) based on the ubuntu.com bugzilla 17569 plus several ubuntuforums.org reports. I will quote those from this year (i.e. after the bugzilla bug report was marked as fixed): http://www.ubuntuforums.org/showthread.php?t=119449&highlight=setkeycodes+e02a+dmesg
http://www.ubuntuforums.org/showthread.php?t=127458&highlight=setkeycodes+e02a+dmesg
http://ubuntuforums.org/showthread.php?t=119499 |
|
| 2006-04-28 08:43:34 |
kko |
None: status |
Confirmed |
Unconfirmed |
|
| 2006-04-28 08:43:34 |
kko |
None: statusexplanation |
Marking as confirmed (for Breezy) based on the ubuntu.com bugzilla 17569 plus several ubuntuforums.org reports. I will quote those from this year (i.e. after the bugzilla bug report was marked as fixed): http://www.ubuntuforums.org/showthread.php?t=119449&highlight=setkeycodes+e02a+dmesg
http://www.ubuntuforums.org/showthread.php?t=127458&highlight=setkeycodes+e02a+dmesg
http://ubuntuforums.org/showthread.php?t=119499 |
Reverting, will let the developers mark this as "confirmed". |
|
| 2006-04-29 09:43:31 |
kko |
None: statusexplanation |
Reverting, will let the developers mark this as "confirmed". |
|
|
| 2006-04-29 09:52:41 |
kko |
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".
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.
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? |
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/hotkey-setup/generic.hk, or removing the keycode from there, or simply stopping hotkey-setup.
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? |
|
| 2006-05-08 07:38:26 |
kko |
None: statusexplanation |
|
Reporting this on "hotkey-setup" doesn't seem to work, trying again. |
|
| 2006-05-08 11:08:21 |
Matthew Garrett |
hotkey-setup: status |
Unconfirmed |
Fix Released |
|
| 2006-05-08 11:08:21 |
Matthew Garrett |
hotkey-setup: statusexplanation |
Reporting this on "hotkey-setup" doesn't seem to work, trying again. |
This is fixed in dapper. A fix will not be released for breezy. |
|
