xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 7 years ago

Closed 6 years ago

Last modified 16 months ago

#923 closed defect (fixed)

AltGr broken after Ctrl-Escape / Escape

Reported by: fladnag Owned by: fladnag
Priority: major Milestone: 0.16
Component: client Version: 0.14.x
Keywords: altgr Cc:

Description (last modified by Antoine Martin)


  • server : debian 8, xpra 0.14.10
  • client : win 7, xpra 0.14.24, from winswitch, but using only xpra_cmd.exe

Keyboard : fr - default

Logs: SERVER and USER have been replaced for security reasons

xpra start :100 -d keyboard
DISPLAY=:100 xterm &
xpra attach ssh:...:100 -d keyboard


  • focus xterm
  • press AltGr}} + {{{3 : OK, shows "#"
  • press Ctrl + Escape: opens windows start menu
  • press Escape: closes start menu
  • press AltGr}} + {{{3 : OK, shows "#"
  • press Ctrl + Escape: opens windows start menu
  • press Escape: closes start menu
  • click on xterm window
  • press AltGr}} + {{{3 : bug, prints "£" instead of "#"
  • press Backspace : bug, prints "ÿ" instead

Attachments (1)

xpra-altgr-bug.zip (94.6 KB) - added by fladnag 7 years ago.

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by fladnag

Attachment: xpra-altgr-bug.zip added

comment:1 Changed 7 years ago by fladnag

Another issue with AltGr (same environment)
AltGr down event persist without up event. So, typing :
a produce æ
b produce ”
c produce ¢
d produce ð
e produce €

in xpra client log, just before that, I saw the following lines :

2015-08-08 12:56:49,299 unexpected message: 49768 / 0 / 0
2015-08-08 12:58:30,700 unexpected message: 992 / 394642 / -1073102706
2015-08-08 13:23:26,219 unexpected message: 49577 / 2 / 0
Last edited 7 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 7 years ago by Antoine Martin

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

Sorry for the long delay in dealing with this bug and thank you for the detailed bug report.
This has uncovered a serious bug which has been there for many years and may have had all sorts of undesirable side effects.

The trivial server side fix is in r11247, and it will be included in the next stable update.

And since I was there, I improved the code a bit more:

  • r11248 makes the code easier to read
  • r11249 should workaround any bugs by using the "big hammer": a full keyboard reset
  • r11250 is a better way of choosing a modifier key to unpress (may also backport this one)
  • r11254 only loops over modifiers lists if they are actually different, after' removing the ones we don't care about

Thought: maybe we should keep track of which modifier keycodes are used?
(at the moment, when we need to add a modifier, we pick the first keycode that matches)

@fladnag: please close when you have time to confirm that this is fixed (will make new beta builds soon)

Last edited 7 years ago by Antoine Martin (previous) (diff)

comment:3 Changed 6 years ago by Antoine Martin

Resolution: fixed
Status: newclosed

Closing as fixed. Feel free to re-open if you still have problems.

comment:4 Changed 6 years ago by fladnag

fix ok in 0.16.0-1 ;o)

comment:5 Changed 16 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/923

Note: See TracTickets for help on using tickets.