We should figure out what the requirements are and avoid showing the shadow buttons in that case.

the code itself is pretty easy, what is difficult is keeping the interface clean between the dialog, the client and the server...

Maybe define a list of options for each session type? Is this too generic for the sake of it?

NX and VNC call self.set_xmodmap(session, user) before any client attaches to set the keymap to the one that was supplied by the client (guessed using xmodmap on *nix clients)

This seems to work in most cases but not always.

Here are some bugs that may be related: ​http://ubuntuforums.org/archive/index.php/t-959411.html

​https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/289918

​https://bugs.launchpad.net/ubuntu/intrepid/+source/xorg-server/+bug/255008

Also related is #82 : on macosx we can't always get xmodmap (if the server is not running this would cause it to start).

We may be able to get it to work with just setxkbmap? (ie: setxkbmap -rules xfree86 -model pc104 -layout us -option "";), provide UI to select the keymap given the list in grep xkb_symbols /usr/share/X11/xkb/symbols/gb? default to current? (setxkbmap -print)

From #139: The solution we have doesn't work in all cases:

• xpra + UK keyboard mapping ends up wrong
• win32 doesn't map properly either?
• osx: we have to guess since the build does not use an X server..

etc.