t61 keyboard under Hardy (Fn, Menu, ThinkVantage keys)

[eldad]

Binary package hint: xkeyboard-config

Menu key (between right Alt and Control) and Fn key (next to left Control) give the same xev output.
I believe this is not supposed to be so as it does not allow distinguishing them for mapping (xmodmap)

KeyPress event, serial 30, synthetic NO, window 0x2600001,
    root 0x13b, subw 0x2600002, time 46299652, (19,57), root:(678,108),
    state 0x10, keycode 227 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x2600001,
    root 0x13b, subw 0x2600002, time 46299652, (19,57), root:(678,108),
    state 0x10, keycode 227 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

ThinkVantage key produces no response

Description: Ubuntu hardy (development branch)
Release: 8.04

[Daniel Sargeant (dsargeant)]

Confirmed with r61

[eldad (eldad-a)]

Please also note that the Fn key is still unique in generating the special brightness, suspend, keyboard light etc...
The Menu key has not this functionality.
The Menu key combined with = and - keys does make icons larger and smaller in rox-filer (as Alt-Gr should) while the Fn key does not.
So there is definitely some difference between the two but I am not sure how a user can use it...

[Robert Persson (ireneshusband)]

I don't know if this is part of the same bug or not, but I'll mention it just in case:

When I set the menu key to be the compose key it has not effect. For instance menu + s + s gives me ss rather than ß. However right-control works just fine as the compose key.

Please post a comment if this is a separate issue so that I can file a separate report for it. Thanks.

[John Karp (johnkarp)]

The sound level buttons (mute, down, and up) produce very strange X events instead of keyevents:

FocusOut event, serial 30, synthetic NO, window 0x3c00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 30, synthetic NO, window 0x3c00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 30, synthetic NO, window 0x3c00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 30, synthetic NO, window 0x0,
    keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

[Bryce Harrington (bryce)]

Not really an xkeyboard-config issue; more of a hotkey problem.
See http://wiki.ubuntu.com/Hotkeys for more help in tracking down hotkey problems.

[John Karp (johnkarp)]

With T61 running 8.10:

'Fn' key:
keycode 151 (keysym 0x1008ff2b, XF86WakeUp)
Incorrect keycode. According to Hotkeys/Troubleshooting page, this indicates a bug in xkeyboard-config.

'Menu' key:
keycode 151 (keysym 0x1008ff2b, XF86WakeUp)
Incorrect keycode, should map to 'Menu' keysym. Therefore, xkeyboard-config problem.

ThinkVantage key:
No xev output.
I can't find the 'input-events' util referred to in that guide, but 'cat /dev/input/event9', corresponding to 'ThinkPad Extra Buttons' in HAL does produce output when the key is pressed. lshal does not show a corresponding 'input.keys' entry, and input.x11_driver = ''.
Then, according to the troubleshooting page, "this is a bug in hal or in some desktop component that should be listening for that event via hal".

Volume control keys:
Still producing the same strange keymap events.

[Steve Langasek (vorlon)]

Please see <https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/287428/comments/16> for an explanation of this issue.