Forwarded from Debian bug 391613
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391613
"When selecting the XDMCP protocol, the keyboard map configured for X.org is ignored so, when typing the login/password in the remote GDM, someone has the unpleasant surprise to notice that the keyboard map has reverted to US.
Additionally, specifying which keyboard map to use in the Local Resources dialog before connecting has no effect either; the keymap reverts to US there too.
While this only affects connections over the XDMCP protocol, it essentially makes tsclient unusable with X11 servers, anywhere outside USA."
"According to <http://www.cygwin.com/ml/cygwin-xfree/2004-10/msg00025.html>, Xnest needs to have the keyboard map's name passed using the -xkbmap option.
Sure enough, looking at the process map confirms that tsclient doesn't:
3501 ? S 0:01 \_ tsclient
3823 ? D 0:00 \_ Xnest :1 -once -geometry 1024x768 -query omena
The cure would apparently be to pass the 2-letter code of the keyboard map selected in the Local Resources using the above option. In this example, it should have been:
Xnest :1 -once -xkbmap fi -geometry 1024x768 -query omena"
Logged In: YES
user_id=979379
Originator: NO
Actually, there is no way to change keymap in Xnest. A possible fix would be to use Xephyr instead of Xnest. Xephyr support all X extensions.