IBM T23: no Num-lock and Scroll-lock
Matthew Flaschen
matthew.flaschen at gatech.edu
Tue Apr 24 09:39:56 UTC 2007
Michael Bach (gmx) wrote:
> Matthew,
> following is what I get reported from "xev":
>
> Pressing and releasing scroll-lock:
>
[snip]
That looks normal
>
> Num-lock:
> KeyPress event, serial 31, synthetic NO, window 0x3800001,
> root 0x44, subw 0x0, time 1064084, (-48,253), root:(696,272),
> state 0x1, keycode 77 (keysym 0xfef9, Pointer_EnableKeys),
> same_screen YES,
> XLookupString gives 0 bytes:
> XmbLookupString gives 0 bytes:
> XFilterEvent returns: False
>
> KeyRelease event, serial 31, synthetic NO, window 0x3800001,
> root 0x44, subw 0x0, time 1064115, (-48,253), root:(696,272),
> state 0x1, keycode 77 (keysym 0xfef9, Pointer_EnableKeys),
> same_screen YES,
> XLookupString gives 0 bytes:
> XFilterEvent returns: False
Hmm. I don't have to push shift, but I get:
KeyPress event, serial 32, synthetic NO, window 0x3a00001,
root 0x3e, subw 0x0, time 586210918, (809,148), root:(813,458),
state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x3a00001,
root 0x3e, subw 0x0, time 586210999, (809,148), root:(813,458),
state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
It's strange that your is saying "Pointer_EnableKeys" (but still 77).
Try making a file /etc/X11/Xmodmap with the contents:
keycode 237 = Num_Lock
Then run:
xmodmap /etc/X11/Xmodmap
If that works, you'll have to put in a startup script. Either way, file
a bug on launchpad.
Matt Flaschen
More information about the kubuntu-users
mailing list