in the following reports I always leave out lines like these to save
sceen space:
root 0x377, subw 0x0, time 1027512667, (515,302), root:(519,358),
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
xev on local X11 session. Pressing Up and Right keys on arrow keypad
(not numeric keypad):
KeyPress event, serial 35, synthetic NO, window 0x4600001,
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
KeyRelease event, serial 38, synthetic NO, window 0x4600001,
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
KeyPress event, serial 38, synthetic NO, window 0x4600001,
state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 38, synthetic NO, window 0x4600001,
state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
xev on vnc4server 4.1.1+X4.3.0-37.1, xvnc4viewer 4.1.1+X4.3.0, pressing
same keys again:
KeyPress event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 98 (keysym 0xff52, Up), same_screen YES,
KeyRelease event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 98 (keysym 0xff52, Up), same_screen YES,
KeyPress event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 102 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 102 (keysym 0xff53, Right), same_screen YES,
xev on local X11 session pressing super+Up and super+Right on arrow
keypad (not numeric keypad). i checked that it is really super+Up by
verifying that it automatically maximizes the window. this way you do
not see the key events in xev. To actually see the keys in xev I
reconfigured my gnome keyboard settings to not use super+Up anymore.
this is the result:
KeyPress event, serial 38, synthetic NO, window 0x3000001,
state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
KeyPress event, serial 38, synthetic NO, window 0x3000001,
state 0x40, keycode 111 (keysym 0xff52, Up), same_screen YES,
KeyRelease event, serial 38, synthetic NO, window 0x3000001,
state 0x40, keycode 111 (keysym 0xff52, Up), same_screen YES,
KeyPress event, serial 38, synthetic NO, window 0x3000001,
state 0x40, keycode 114 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 38, synthetic NO, window 0x3000001,
state 0x40, keycode 114 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 38, synthetic NO, window 0x3000001,
state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
xev on vnc4server 4.1.1+X4.3.0-37.1, xvnc4viewer 4.1.1+X4.3.0, pressing
same keys again (with super):
KeyPress event, serial 33, synthetic NO, window 0x3200001,
state 0x0, keycode 255 (keysym 0xffeb, Super_L), same_screen YES,
KeyPress event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 98 (keysym 0xff52, Up), same_screen YES,
KeyRelease event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 98 (keysym 0xff52, Up), same_screen YES,
KeyPress event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 102 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 102 (keysym 0xff53, Right), same_screen YES,
KeyRelease event, serial 35, synthetic NO, window 0x3200001,
state 0x0, keycode 255 (keysym 0xffeb, Super_L), same_screen YES,
analysis of results:
keycodes on local X11 and vnc are different.
keysym on local X11 and vnc are the same.
see the difference on the Super_L keypress. keycode is 255 on vnc!. is
255 a legal keycode? it somehow looks like -1.
running gnome keyboard settings on local x11 i can enter new key
sequences consisting of super+anything. when trying to do so on vnc,
once you press the super key, "Super L" will be displayed as key. this
means super is not seen as a modifier. it is instead seen as a "final"
key just like hitting a normal alphabetic key.
running xmodmap on x11 local:
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce),
Hyper_L(0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
running xmodmap on vnc:
xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x40), Alt_R (0x71)
mod2
mod3
mod4
mod5
see that there is no Super stuff on xmodmap vnc.
i am not an expert in vnc/x11/keyboard stuff.
For now i simply disable Super-Up/Down in gnome keyboard settings as
suggested in the bugreport, but still i do not understand, why gnome
thinks the user presses super keys even though he does NOT press the
super keys. I don't know how to fix this also i do not know if it is a
gnome or a vnc problem.
but it is an important bug because it makes vnc non-usable (without
googling for this dirty fix)!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
