On 05/18/2016 02:29 PM, Chris Murphy wrote:
On Wed, May 18, 2016 at 12:28 PM, Tom Killian
<tom.killian(a)gmail.com> wrote:
>> It's an Apple keyboard, maybe six years old but I don't ever recall
>> seeing an Apple keyboard with numlock because there was never such a
>> thing as navigation by keypad on Macs.
>
>
> Maybe run xev and see what keystrokes it's actually sending.
KeyPress event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813446, (626,458), root:(660,1445),
state 0x0, keycode 84 (keysym 0xff9d, KP_Begin), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813526, (626,458), root:(660,1445),
state 0x0, keycode 84 (keysym 0xff9d, KP_Begin), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813630, (626,458), root:(660,1445),
state 0x0, keycode 85 (keysym 0xff98, KP_Right), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813685, (626,458), root:(660,1445),
state 0x0, keycode 85 (keysym 0xff98, KP_Right), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813829, (626,458), root:(660,1445),
state 0x0, keycode 79 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 813910, (626,458), root:(660,1445),
state 0x0, keycode 79 (keysym 0xff95, KP_Home), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 814014, (626,458), root:(660,1445),
state 0x0, keycode 80 (keysym 0xff97, KP_Up), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 814094, (626,458), root:(660,1445),
state 0x0, keycode 80 (keysym 0xff97, KP_Up), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 814190, (626,458), root:(660,1445),
state 0x0, keycode 81 (keysym 0xff9a, KP_Prior), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x1200001,
root 0x4c7, subw 0x0, time 814270, (626,458), root:(660,1445),
state 0x0, keycode 81 (keysym 0xff9a, KP_Prior), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
In any case, numlockx does put it into a mode where the keypad numbers
come through. Where I'd think GNOME Shell would do something similar
by default because, well, who navigates by keypad these days?
This is a wild guess, but it may have something to do with the keymap.
As someone else mentioned, I believe the default is "numlock enabled",
but if you're using a keyboard (or keymap) that doesn't have a numeric
pad, that default may not mean anything so numlock is NOT enabled.
Weird, but there's a LOT of stuff in Gnome that's weird (which is one
reason I do not use it).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Political Correctness: The insane doctrine that postulates that it -
- is entirely possible to pick up a turd by the clean end. -
----------------------------------------------------------------------