xpra icon
Bug tracker and wiki

Opened 3 years ago

Last modified 7 weeks ago

#1465 closed defect

Bad keyboard translations and some modifier keys not working in combos — at Version 1

Reported by: vival Owned by: vival
Priority: major Milestone: 2.2
Component: keyboard Version: trunk
Keywords: Cc:

Description (last modified by Antoine Martin)

I'm experiencing two problems with the keyboard.

My setup:

  • server machine: Arch Linux x64, no DE, WM is herbstluftwm, xpra v1.0.3-r15051, xorg server 1.19.2-1
  • client machine: Windows 7 x64, xpra v1.0.3-r15051
  • server cmd: xpra shadow :0
  • client cmd: xpra attach ssh:---:0

Here is a log from using "-d keyboard" where I press all of the problem keys once in the order of "< > | alt+e": attachment/ticket/1465/t-o.log
Here is the output of "xmodmap -pke": attachment/ticket/1465/t--.txt

First problem is that the keys < and | are translated to > key. This problem only happens if I attach a shadow display, not regular xpra display.

Xev output for these three keys are all the same

KeyPress event, serial 35, synthetic NO, window 0x4600001,
    root 0x44f, subw 0x0, time 73765672, (-289,434), root:(994,470),
    state 0x1, keycode 94 (keysym 0x3e, greater), same_screen YES,
    XKeysymToKeycode returns keycode: 60
    XLookupString gives 1 bytes: (3e) ">"
    XmbLookupString gives 1 bytes: (3e) ">"
    XFilterEvent returns: False

Second problem is that some modifier keys show up in xev but don't actually work. This problem happens whether I attach a shadow display or regular xpra display.

Control and shift have no problem. Alt has a problem.

KeyPress event, serial 35, synthetic NO, window 0x4600001,
    root 0x44f, subw 0x0, time 73724840, (-89,410), root:(1194,446),
    state 0x0, keycode 134 (keysym 0xffea, Alt_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

It shows up in xev but doesn't work in combos, pressing something like Alt+e will act as if I had pressed Alt then e separately. And when I assign a key to a modifier key with xmodmap, which I have to do for the Super key to ensure I don't activate Windows shortcuts, the same thing will happen, shows up in xev, but doesn't work in combos.

Change History (11)

Changed 3 years ago by Antoine Martin

Attachment: t-o.log added

keyboard debug log

Changed 3 years ago by Antoine Martin

Attachment: t--.txt added

xmodmap -pke

comment:1 Changed 3 years ago by Antoine Martin

Description: modified (diff)
Owner: changed from Antoine Martin to vival

Can you please include the matching server "-d keyboard" log?

And any other useful information from wiki/Keyboard.

(I have converted the logs to attachments so they don't bitrot)

Changed 3 years ago by vival

Attachment: xpra_keyboarderr_client.log added

-d keyboard log from client

Changed 3 years ago by vival

Attachment: xpra_keyboarderr_server.log added

-d keyboard log from server

Changed 3 years ago by vival

Keymap_info.exe run on client machine

Changed 3 years ago by vival

keymap.py run inside xpra session

Changed 3 years ago by vival

setxkbmap -print run inside xpra session

Changed 3 years ago by vival

setxkbmap -query run inside xpra session

Changed 3 years ago by vival

xmodmap -pke run inside xpra session

Changed 3 years ago by vival

xmodmap -pm run inside xpra session

Note: See TracTickets for help on using tickets.