This is an old revision of the document!
For those who want to find reasons for certain behavious of X2Go, read here: How To Debug or Troubleshoot your x2go installation
No even though X2go uses the same libraries, X2go aims for an even greater integration into the Linux environment. It’s not possible to use NX client to log on to a X2go server and vice versa.
Yes - the NX libraries of X2go are actually the most recent versions of NXv3 libs available. NoMachine has dropped the NXv3 development branch completely and closed source on NXv4 .
Due to these circumstances in the future the X2go project will be upstream source for NXv3 libs for quite some distributions like Debian or Ubuntu.
In former times the NX libs shipped with X2go installed into an X2go'ish location so that they would not interfere with the original NX libraries.
Nowadays the NX libs shipped with X2go work as a replacement for the NXv3 that are not maintained by NoMachine anymore.
(This FAQ article has been written by Mike Gabriel, if someone does not agree with the given information on NoMachine, please be so kind to contact me, so that we can discuss it and possibly correct errors in the given information).
LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only.
However, X2go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2go - enable the transport of whole desktop sessions over a narrow bandwith connection through the internet.
Further bonuses of X2go are that you can pause a desktop session and take it to a different thin client for further use.
Both packages (x2goserver-home, x2goserver-one) are obsolete as of April 2011. They have been removed from the current .deb repositories and they should not be used anymore (in fact they break your system). On .deb based system they will automatically be uninstalled with an update of the x2goserver package.
x2goserver currently does neither have any group membership restriction any more as former versions had. This may well be re-introduced, though, if someone picks up work on that.
The obsolete x2goserver-home package added all known users on the server system to the group x2gousers which made some people nervous when testing X2go on production systems . For this reason we have dropped the auto-adding of users to groups in Apr 2011.
No. The postgres database is only needed if you are planing to use more than one connected server (server array). By default x2goserver installs with SQLite support enabled. To set up X2go with PostgreSQL as DB backend you have to edit the x2goserver's configuration in /etc/x2go.
So long as X2Go uses the NX protocol exclusively for remote display and keyboard/pointer input, X2Go cannot support Wayland or Mir. (Audio and file/printer sharing are handled by separate protocols.) This is because NX works with the X11 protocol, rather than using an entirely separate protocol like SPICE and VNC do. (NX improves X11 performance by caching the X11 traffic, compressing it, and eliminating the X11 “round-trips”.)
See the answer to the last question.
Although some tools (e.g. Gnome Keyboard Indicator) might have trouble changing the layout, you should be able to change the keyboard layout using setxkbmap.
setxkbmap de setxkbmap us
Some people have asked for font size customizations in X2Go session windows. Please use the DPI value in the session setup to customize font sizes within your X2Go sessions:
Add users that shall be granted X2go file and folder sharing functionality to the fuse group on your system. For user foo this may look like this at the command line:
$ adduser foo fuse
Yes, you can find it on our install page here: Installing X2Go
Yes, you can find it on our install page here: Installing X2Go
To set a print target, you'll need x2goclient
. For example you can use the RDP tunneling feature of X2go.
At this time libssh, the ssh library used by x2go is unable to work with an ECDSA key. However you may use an RSA key -if you need to- or go with the ssh default authenticating method using the remote user's password.
Unfortunately, Unity on Ubuntu 12.10 will not work with X2Go in the foreseeable future.
This is because Ubuntu 12.10 and later no longer offer Unity-2D; they only offer regular Unity. When selecting Unity in an x2go client, you are actually selecting Unity-2D. However, regular Unity requires 3D support. X2Go cannot support 3D because X2Go is currently based on the NX libraries, which do not support 3D.
One workaround is to remain on Ubuntu 12.04 LTS, which is supported until April 2017. Another workaround is to install one of the other desktop environments that is listed in your X2Go Client. You can do so without uninstalling Unity. Follow this link for instructions on installing other desktop environments.
Also, see our page about Desktop Environment Compatibility
See our page about Desktop Environment Compatibility