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.
- when connecting over high latency links, use the
--no-keyboard-syncoption to prevent keys from repeating. This toggle is also accessible from the system tray menu. (this switch may cause other problems though) - keyboard shortcuts: #1657
- US layout and most common layouts should work OK
- if starting xpra from an environment which has non-standard input methods, this can interfere, see #286
- input methods don't work by default: #634
- Supporting multiple layouts and switching layouts reliably and/or manually: #230, #166, #86, #1607, #1665, #1380
- Multiple keys / meta: #668, #759
- Input grabs: #139
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 found in the
xpra toolbox - active keyboard layout(s)
- input methods
- keyboard related configuration setup/files
- keyboard type
- client and server log output with the
-d keyboarddebugging switch - whether the bug is also present with / without the
--no-keyboard-syncswitch - X11 systems:
**
setxkbmap -printandsetxkbmap -query(both directly in the client if it supports those commands and in the xpra session) **xmodmap -pkeandxmodmap -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,keyname2on the server to log the keyboard mapping process for those keys - X11 servers:
xevoutput of the misbehaving key events