Keyboard

Keyboard handling is an area that is constantly seeing improvements and bug fixes. That’s because each platform does things slightly differently and xpra has to somehow convert this data into meaningful keyboard events on the remote end.

Common Issues

Reporting Bugs

First, please check for existing issues that may match your problem. Failing that, make sure to read the reporting bugs guidelines and generally you will need to include (only those that apply): * try the keyboard debugging tool which can be launched using xpra keyboard-test or from the xpra toolbox * active keyboard layout(s) * input methods * keyboard related configuration setup/files * keyboard type * client and server log output with the -d keyboard debugging switch * whether the bug is also present with / without the --no-keyboard-sync switch * X11 systems: ** setxkbmap -print and setxkbmap -query (both directly in the client if it supports those commands and in the xpra session) ** xmodmap -pke and xmodmap -pm (again on both) ** xkbprint -label name $DISPLAY * MS Windows: Keymap_info.exe * if the problem is affecting specific keys, you may want to use the environment variable XPRA_DEBUG_KEYSYMS=keyname1,keyname2 on the server to log the keyboard mapping process for those keys * X11 servers: xev output of the misbehaving key events