Xpra: Ticket #1373: shared mode keyboard conflicts

Follow up from ticket:41#comment:39. Each new client connection overwrites the keymap.

We need to keep track of who owns the keyboard (separate from "ui-driver"?) and either:

change the keymap on the fly when a new user interacts with the session - hard, may not work well as setting the keymap is partly asynchronous
translate keyboard events for the "other" clients

Sat, 18 Feb 2017 10:01:24 GMT - Antoine Martin: owner changed

owner changed from Antoine Martin to alas

Done in r15110. We can now connect multiple clients with completely different keymaps (different OS, different layout, etc) and each client should still be able to use most of their keys.. The first client to connect will still "own" the keymap, which means that we won't be adding new layouts from the secondary clients.

How to test:

start a server with sharing enabled
connect a win32 client (for example) with a 'fr' layout (which has 'a' and 'q' keys swapped)
connect a linux client with a 'us' layout

Both clients should be able to use the keyboard and have the correct keys appear in applications (ie: xterm).

Note: this ticket is not meant to give 100% coverage of keyboard input when sharing is enabled (which may not be achievable anyway), just to make it a lot more usable than before.

Tue, 20 Jun 2017 19:58:13 GMT - J. Max Mena: status changed; resolution set

status changed from new to closed
resolution set to fixed

Tested (trunk Fedora 25 server, and Fedora 25 and Win8.1 clients) and it seems to behave, at least with my two identically-layed-out ENG-US keyboards. Closing

Wed, 06 Dec 2017 10:47:42 GMT - Antoine Martin:

Follow up: #1716

Sat, 23 Jan 2021 05:22:28 GMT - migration script:

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