Good idea to use xev to determine what X is seeing.
I have two machines with full-size US keyboards, including the keypad. Both
are running Ubuntu 8.10 and Gnome 2.24 with the latest packs installed.
Both have vino enabled and I am using vinagre to connect to the remote
server.
I used the command "xev | grep KeyPress -A 2 -B 2" to filter out
keypresses. I pressed the keypad 4, keypad 6, and NumLock key sequential on
both computers. The results are below, one line for each key and if
multiple KeyPress events were generated for a key, they are seperated by a
semicolon ";". Only keys on the local computer are actually being pressed.
Local computer only: NumLock ON
4: 0xffb4, KP_4
6: 0xffb6, KP_6
NL: 0xff7f, Num_Lock
Local computer only: NumLock OFF
4: 0xff96, KP_Left
6: 0xff98, KP_Right
NL: 0xff7f, Num_Lock
So from this it looks like the Local NumLock state is being ignored and that
some part of the VNC is trying very hard to ensure that the Remote X server
is seeing keypresses as if NumLock were off.
Incidentally, this is the same setup that was seeing Mouse Keys being
enabled when using VNC, though I did not experience it when I did these
test.
Good idea to use xev to determine what X is seeing.
I have two machines with full-size US keyboards, including the keypad. Both
are running Ubuntu 8.10 and Gnome 2.24 with the latest packs installed.
Both have vino enabled and I am using vinagre to connect to the remote
server.
I used the command "xev | grep KeyPress -A 2 -B 2" to filter out
keypresses. I pressed the keypad 4, keypad 6, and NumLock key sequential on
both computers. The results are below, one line for each key and if
multiple KeyPress events were generated for a key, they are seperated by a
semicolon ";". Only keys on the local computer are actually being pressed.
Local computer only: NumLock ON
4: 0xffb4, KP_4
6: 0xffb6, KP_6
NL: 0xff7f, Num_Lock
Local computer only: NumLock OFF
4: 0xff96, KP_Left
6: 0xff98, KP_Right
NL: 0xff7f, Num_Lock
Local: Numlock ON, Remote: NumLock ON
4: 0xff7f, Num_Lock; 0xff96, KP_Left; 0xff7f, Num_Lock
6: 0xff7f, Num_Lock; 0xff98, KP_Right; 0xff7f, Num_Lock
NL:
Local: Numlock ON, Remote: NumLock OFF
4: 0xff96, KP_Left
6: 0xff98, KP_Right
NL:
Local: Numlock OFF, Remote: NumLock ON
4: 0xff7f, Num_Lock; 0xff96, KP_Left; 0xff7f, Num_Lock
6: 0xff7f, Num_Lock; 0xff98, KP_Right; 0xff7f, Num_Lock
NL:
Local: Numlock OFF, Remote: NumLock OFF
4: 0xff96, KP_Left
6: 0xff98, KP_Right
NL:
So from this it looks like the Local NumLock state is being ignored and that
some part of the VNC is trying very hard to ensure that the Remote X server
is seeing keypresses as if NumLock were off.
Incidentally, this is the same setup that was seeing Mouse Keys being
enabled when using VNC, though I did not experience it when I did these
test.