[Bug 17569] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on isa0060/serio0).

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17569
Ubuntu | linux





------- Additional Comments From Joerg-Cyril.Hoehle at T-Systems.com  2005-11-09 13:38 UTC -------
For me it's my german keyboard [sharp# + quote'] key, next to the
reduced-size return key and hjklöä# which ceases to work and causes
the message since my upgrade from Hoary to Breezy.
The german keyboard typically has extra keys not found on a US kbd.

atkbd.c: Unknown key pressed (raw set 2, code 0x5d on isa0060/serio0)

/etc/init.d/hotkey-setup stop puts this misbehaviour to an end.

Curiously, I rebooted the laptop several times since doing so, and the
key continues to work. I had expected to need to repeat after every
boot.  Are key scan codes are stored in non-volatile memory??

Oddly, showkey -s reports scancode 2b for this '#' key. Could this
have been an intermittent fault?!?

Here's another observation
# sudo getkeycodes
"Einfache Scancodes xx (hexadezimal) und Tastencodes (dezimal)
for 1-83 (0x01-0x53) scancode equals keycode"
I'm pretty sure that I've seen it report
for 1-1 (...) scancode equals keycode
    ^^^ back when the bug was seen!
Whereas the manpage says: "It is hardwired in the current kernel that  in
the  range  1-88 (0x01-0x58) keycode equals scancode."
              ^^
Why is it different from the manpage?

dmidecode reports:
Handle 0x0001
        DMI type 1, 25 bytes.
        System Information
                Manufacturer: FUJITSU SIEMENS
                Product Name: LIFEBOOK C1110
                Version:
                Serial Number: 0000000000
                UUID: 286D...
                Wake-up Type: Power Switch

BTW, I'm quite pleased that with Breezy, the system know reacts to the
Fn+F8/F9 keys to de-/increase the speaker volume.


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.