[X2Go-User] Keyboard mapping issues with Windows client
Roderick Johnstone
rmj at ast.cam.ac.uk
Thu Jan 9 14:33:49 CET 2014
Just to round this out, in case it might be of use to anyone else, I
eventually got a working system as documented in comment 19 here:
https://bugzilla.redhat.com/show_bug.cgi?id=1033876
Roderick
On 29/12/13 22:14, Mike Gabriel wrote:
> On So 29 Dez 2013 20:48:15 CET, Roderick Johnstone wrote:
>
>> 1) For the simple xterm session setting the layout to "auto" or
>> checking the box "Keep current keyboard settings" is not working.
>
> Use auto for the keyboard model, not the layout!!! The "Keep current
> keyboard settings" checkbox actually means: don't do anything
> keyboard'ish (ends up in pc104/us keyboard map) and let the user handle
> that in his/her desktop session keyboard setup tool.
>
>> 2) KDE is possibly overriding the already set keyboard map with a US
>> layout.
>
> The overrides have to be switched off. Otherwise you have two tools
> trying to play with setxkbmap!!!
>
>> Can you confirm that its possible (for you) to get a KDE session with
>> the correct keyboard mapping that is not the default?
>
> I mostly test from Linux clients, sometimes from Windows machines. X2Go
> Server systems are mostly Debian. With those combinations, I always get
> a German keyboard even with the compose key being mapped correctly.
>
> Mike
>
More information about the x2go-user
mailing list