On 4/9/13 2:15 PM, Mike Gabriel wrote:
on the Mac of a colleagues of mine I have seen setxkbmap (which is used in x2gosetkeyboard) crash when applying the config of ~/.x2go/<session-name>/keyboard.
I assume this is on the x2go server. It at least appears that way.
Maybe there is a way of testing with the keyboard file, setxkbmap and x2gosetkeyboard for someone of you who is using a Mac. I am not sure if that will bring up a solution, but it will be a starting point.
On my server I seem to have a few stale session directories hanging around plus the currently active session. The current session is published apps. The others are either desktops or xdmcp. In all of the session directories except the published apps, I don't have a keyboard file, instead I have a directory. And in x2gosetkeyboard I came across this:
# if there is a directory at the location of the keyboard file, we consider this as blocking this script if [ -d ${X2GO_CLIENT_KBD_FILE} ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "${X2GO_CLIENT_KBD_FILE} is blocked, not setting keyboard parameters from client-side settings" rm -Rf ${X2GO_CLIENT_KBD_FILE} exit 0 fi
So in those instances it appears nothing is being done with the keymap.
As a side note, I see several calls to x2gosyslog in x2gosetkeyboard. Nothing is being logged from x2gosetkeyboard, however. I assume there is an option I need to enable, but as I just now learned that there is such a command, I haven't looked into enabling it as yet.
Feel free to meet up on IRC (#x2go on irc.freenode.net) and use our channel to track this issue down together.
Greets, Mike