This current X mapping is defined by:
/etc/X11/xkb/keycodes/xfree86: <NMLK> = 77;
and then:
/etc/X11/xkb/symbols/pc: key <NMLK> { [ Num_Lock, Pointer_EnableKeys ] };
I think I now understand what's happening; Internally the ThinkPad controller is converting Shift+ScrLock to NumLock, but of course the Shift is still getting passed through to X, so this is what eventually gets us the:
Shift+NumLock
key-event, when it shouldn't be. Mmmm.
This current X mapping is defined by:
/etc/ X11/xkb/ keycodes/ xfree86:
<NMLK> = 77;
and then:
/etc/ X11/xkb/ symbols/ pc:
key <NMLK> { [ Num_Lock, Pointer_EnableKeys ] };
I think I now understand what's happening; Internally the ThinkPad controller is converting Shift+ScrLock to NumLock, but of course the Shift is still getting passed through to X, so this is what eventually gets us the:
Shift+NumLock
key-event, when it shouldn't be. Mmmm.