Acer Aspire 5920G Fn keys not working correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal-info (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hotkey-setup
Worked fine in hardy, doesn't work in Intrepid beta full updated (2008-12-10).
I boot to recovery mode, just console, so no X involved.
I press Fn+right arrow (= brightness up) and the character "?" is echoed. The brightness does increase, but three times, like I had pressed the key 3 times.
If I do this under X, it's exactly the same, only I see the echoed character as "±".
Fn+left arrow (= brightness down) decreases the brightness 3 times without echoing any character.
Back to plain console, if I switch the keyboard to Greek (=shift+alt), everything works OK!!!
No echoed characters, brightness increasing/
Then when I switch back to English, sometimes it remains fixed, other times it's happening again.
Switching keyboard languages in X doesn't make any difference.
There are other keys misbehaving (like, when I'm back to English in console, backspace may be echoing a diamond character instead of deleting the previous char), but I'd better keep it focused on the brightness keys.
> sudo dmidecode -s system-manufacturer
Acer, inc.
> sudo dmidecode -s system-product-name
Aspire 5920G
> sudo dmidecode -s system-version
Not Applicable
> showkey
# A *single* Fn+Left arrow pressing/releasing:
keycode 224 press
keycode 224 release
keycode 224 press
keycode 224 release
keycode 224 press
keycode 224 release
# A *single* Fn+Right arrow pressing/releasing:
keycode 118 press
keycode 118 release
keycode 225 press
keycode 225 release
keycode 225 press
keycode 225 release
> showkey -s
# A *single* Fn+Left arrow pressing/releasing:
0xe0 0x4c 0xe0 0xcc
0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc
# A ***single*** Fn+Right arrow pressing/releasing:
0xe0 0x4e 0xe0 0xce
0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4
I probably don't need to include this, because I'm mainly talking about the console, but anyway,
> setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+
xkb_types { include "complete" };
xkb_compat { include "complete+
xkb_symbols { include "pc+us+
xkb_geometry { include "pc(pc105)" };
};
Kind regards,
Alkis Georgopoulos
Confirming the bug remains in final release of II 8.10. I see exactly this behaviour with my 5920G.
Charlie