Hi Orion,
----- Original message -----
On 11/28/2013 01:46 AM, Mike Gabriel wrote:
Hi Orion,
On Do 28 Nov 2013 01:12:18 CET, Orion Poplawski wrote:
This in x2gostartagent seems wrong:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" != "auto" ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "blocking creation of agent's keyboard file ${SESSION_DIR}/keyboard as requested by session startup command" mkdir -p ${SESSION_DIR}/keyboard fi
In the normal case, X2GO_SET_KBD is 1 and the type is specified as pc105/us or pc105/gb, etc. Since X2GO_KBD_TYPE != auto it does not set the keyboard setttings.
This is a bit hacky, I agree. Let me start from the beginning...
The ~/.x2go/<session>/keyboard file gets created by x2goagent. Always. It is a file containing settings for the client-side keyboard. This parameter in this file can be used to configure the session keyboard automagically.
Now, we have three different keyboard setup types (actually four):
- do not do anything about keyboard setup
-> X2GO_SET_KBD = 0 -> X2GO_KBD_TYPE = null/null (or so)
- set a keyboard specified in X2Go Client
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = pc105/de (or so)
So, in this case, how are the keyboard settings supposed to be applied?
I still owe you an answer to this...
The keyboard layout and the variant (Python X2Go only) in this case will get set via the client. Scan for setxkbmap in onmainwindow.cpp of X2Go Client for details.
The X2GO_KBD_TYPE will be passed to nxagent, directly.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148
GnuPG Key ID 0x25771B13 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de