X2GO Tricks

Sessions do not logoff correctly

Due to this bug [http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=914] your X2Go sessions might not logoff correctly. The script that initiates the session spits out many log lines that might confuse X2go. A simple workarround is to create a custom session script and redirect the log output either to a file or to /dev/null and then point your X2Go-client to this custom script.

Here is a sample script for an XFCE session:

#!/bin/sh
#
#xfce4-session spits out quite a bit of text during logout, which I guess
#confuses x2go so we would get a black screen and session hang.
#adding redirect to a logfile like "~/logfile" or "/dev/null" nicely solved it
# see http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=914
/usr/bin/xfce4-session > /dev/null

See [http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=914] for more information.

'Do not use the workarround to add killall -q x2goagent || true at the end of your script!'

Shared folders do not mount (Windows Clients)

The ssh-daemon used by the X2go windows client uses depreceated ssh-dss keys by default and because Arch does not accept them your shared folders will not mount. Check out this link [http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1009] for more information. A quick and dirty fix is to remove Cipher=blowfish from /usr/bin/x2gomountdirs like this:

# mv /usr/bin/x2gomountdirs /usr/bin/x2gomountdirs.bak
# sed -i 's/Cipher=blowfish\,//g' /usr/bin/x2gomountdirs

and on the windows side do the following:

C:\Program Files (x86)\x2goclient\ssh-keygen -b 2048 -t rsa

And simply replace c:\Users\User\.x2go\etc\ssh_host_dsa_key and c:\Users\User\.x2go\etc\ssh_host_dsa_key.pub with the newly generated key files.

Other workarrounds from [http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1009] might help, too.

public/linux/x2go/x2gosetup.txt · Last modified: 2016/06/27 13:32 (external edit)
CC Attribution-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0