On Thu, 2012-02-02 at 11:56 +0100, Oleksandr Shneyder wrote:
Hello X2Go users,
I want to describe some changes we made in X2Go recently.
== Multi display support features. == There are two new features in X2Go to support desktops with more then one physical display.
- Run X2Go Session in "full screen" mode on one of several physical displays. With this feature you can use one of your physical monitors to display X2Go session in "full screen" mode. On this photo you can see a Windows 7 notebook with a connected VGA monitor running X2Go Session on display 2: http://www.x2go.org/_media/news:two_sess.png
You can configure this feature using Session Preferences dialog in X2Go client: http://www.x2go.org/_media/news:multidisp_set.png
Push "Identify all displays" button to find out the numbers of a physical displays: http://www.x2go.org/_media/news:ident_dsip.png
- Using two or more physical displays as one large virtual display (Xinerama) The advantage of Xinerama feature is to only maximize windows to the dimensions of the active physical display. This can be very useful not only for thinclients with more then one physical displays, but also if user stretch their X2Go sessions over more then one display in "window" mode.
X2Go Session running 3 maximized LibreOffice windows is stretched over 3 physical displays: http://www.x2go.org/_media/news:xinerama.png
Xinerama configuration of X2Go session will be automatically updated every time when user moving or resizing his X2Go Session window.
==Verifying if port is free before resuming X2Go Session ==
On start of an X2Go session 3 tcp ports for ssh tunnels (graphic, sound, sshfs) are reserved. The values of these ports are stored in the X2Go session database and used by X2Go clients every time an X2Go session gets resumed. Sometimes it can happen that one of these ports is already used by another application after the session had been suspended. As result, X2Go client will be unable to resume such session or start sound or sshfs tunnel. To avoid this problem X2Go server (>= 3.1.0.0) will verify if these ports are still unused before the session will be resumed. In other case new ports will be reserved. The new port values will be updated in database and sent to the X2Go client.
IMPORTANT: Older versions of X2Go client will be compatible with newest X2Go servers. If ports have changed between suspend and resume of a session, older x2goclients will try to reconnect and fail. But on the next attempt, X2Go client will retrieve the updated port values from the X2Go session database. <snip> Very much appreciated. Thank you - John