- 1 Installation
- 2 Server configuration
- 3 Desktop Shadowing
- 4 Client configuration
- 5 Troubleshooting
- 6 See also
- - X2Go server
- - X2Go client based on Qt4
Configure Secure Shell daemon
X2Go uses Secure Shell in order to work, so you need to configure sshd daemon to allow X11 forwarding and then start it first. Follow the instructions at Secure Shell#X11 forwarding and Secure Shell#Daemon management.
If you are using other than POSIX (C) locale, you may want to add the following line to configuration file
# Allow client to pass locale environment variables AcceptEnv LANG LC_*
Load fuse kernel module
In order for the server to be able to access files on the client computer you should load a
fuse kernel module.
Setup SQLite database
Run the following command on the server to initialize the SQLite database (which is required in order for the x2go server to work):
# x2godbadmin --createdb
Start X2Go server daemon
Now all you need to do is start
To gain access to the "local desktop" (as opposed to a unique session/desktop environment) you need to install AUR. Then, launch
Note, you do not need x2godesktopsharing to access "local desktop" of user "foo" by user "foo". x2godesktopsharing is for accessing "foo"'s desktop by "foo2" user. Just choose "Connection to local desktop" in "session type" in x2goclient.
Make sure you can open an SSH session from the client to the server:
$ ssh username@host
Then run X2Go client itself:
You can now create several sessions, which then appear on the right side and can be selected by a mouse click. Each entry consists of your username, hostname, IP, and port for SSH connection. Furthermore you can define several speed profiles (coming from modem up to LAN) and the desktop environment you want to start remotely.
Do not simply choose the defaults of KDE or Gnome, since the executables startkde and startgnome are usually not in the
$PATH when logging in using SSH. Use full paths to startkde or startgnome. You can also start openbox or another window manager.
You should be asked for your password for your user at the server now and after login you will see the X2Go logo for a short time, and the desktop.
Exchange data between client and server (desktop)
On the X2Go client (e.g. laptop) local directories could be shared. The server will use fuse and sshfs to access this directory and mount it to a subdirectory media of your home directory on the server. This enables you to have access to laptop data on your server or to exchange files. It is also possible to mount these shares automatically at each session start.
To leave a session temporarily
Another special feature of X2Go is the possibility of suspending a session. This means you can leave a session on one client and reopen it even from another client at the same point. This can be used to to start a session in the LAN and to reopen it later on a laptop. The session data are stored and administered in a SQLite database on the server in the meanwhile. The state of the sessions is protocolled by a process named x2gocleansessions.
If the following error appears:
Authentification Failed: The host key for this server was not found but an othertype of key exists. An Attacker might change the default server key to confuse your client into thinking the key does not exist
Delete the servers entry from
~/.ssh/known_hosts file and retry to authenticate.
No selection screen in x2goclient
A regression in
-u flag, as done in
Sessions do not logoff correctly
Due to this bug the 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
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 bug report for more information.
This can be solved on the windows side by generating different type of key:
C:\Program Files (x86)\x2goclient\ssh-keygen -b 2048 -t rsa
And simply replace
c:\Users\User\.x2go\etc\ssh_host_dsa_key.pub with the newly generated key files.
Other workarrounds from  might help, too.
Workaround for failing compositing window manager for remote session
This is useful for situations, when the computer running x2goserver is used also for local sessions with e.g. compiz as the window manager. For remote connections with x2goclient, compiz fails to load and metacity should be used instead. The following is for GNOME, but could be modified for other desktop environments. (Getting compiz ready is not part of this how-to.)
[Desktop Entry] Type=Application Encoding=UTF-8 Name=gnome-wm-test Exec=/usr/local/bin/gnome-wm-test.sh NoDisplay=true
Create script /usr/local/bin/gnome-wm-test.sh:
#!/bin/sh # Script for choosing compiz when possible, otherwise metacity # Proper way to use this script is to set the key to mk-gnome-wm # /desktop/gnome/session/required_components/windowmanager xdpyinfo 2> /dev/null | grep -q "^ *Composite$" 2> /dev/null IS_X_COMPOSITED=$? if [ $IS_X_COMPOSITED -eq 0 ] ; then gtk-window-decorator & WM="compiz ccp --indirect-rendering --sm-client-id $DESKTOP_AUTOSTART_ID" else WM="metacity --sm-client-id=$DESKTOP_AUTOSTART_ID" fi exec bash -c "$WM"
Modify the following gconf key to start the session with gnome-wm-test window manager:
$ gconftool-2 --type string --set /desktop/gnome/session/required_components/windowmanager "gnome-wm-test"