User Tools

Site Tools


doc:release-notes-mswin:x2goclient-4.0.5.0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

doc:release-notes-mswin:x2goclient-4.0.5.0 [2015/07/31 13:18] (current)
mikedep333 created
Line 1: Line 1:
 +====== Windows-Specific Release notes for X2Go Client 4.0.5.0 ======
  
 +===== Major Windows-specific changes since 4.0.4.0-2015.06.24 =====
 +
 +  * OpenSSL update to fix CVE-2015-1793 (announced on 2015-07-09)
 +  * bug #883 has been fixed - Window Decorations gone when resuming on smaller screen
 +  * The above fix also changes the behavior of "Use Whole Display"​ mode
 +  * bug #696 has been fixed - **see important notes below**
 +
 +The X2Go project believes that X2Go Client for Windows 4.0.4.0-2015.06.24 and prior are affected by CVE-2015-1793 when connecting to a session broker via HTTPS. Therefore, users that connect to session brokers via HTTPS are encouraged to upgrade to 4.0.5.0 ASAP.
 +
 +Note that there will be no more updates, including security updates, for 4.0.4.0. You must upgrade to 4.0.5.0 to continue receive future security updates.
 +
 +===== Important notes on resuming sessions started from 4.0.4.0 or earlier===== ​
 +
 +The gist of bug [[http://​bugs.x2go.org/​cgi-bin/​bugreport.cgi?​bug=696|bug #696]] is that an X2Go Session started from X2Go Client for Windows 4.0.4.0 (and many/all earlier versions) could not be resumed on Linux or Mac clients. It also could not be resumed from X2Go Client for Windows under certain conditions (see the list of conditions below.)
 +
 +When a session cannot be resumed, you would see the error message:
 +<​code>​
 +Failed to restore all the required visuals.
 +Cant't resume the NX session on this display.
 +</​code>​
 +
 +**However, sessions affected by this issue can be resumed by the client from where it was started, or from other clients running X2Go Client for Windows 4.0.4.0 (or earlier) under the certain conditions, even after you failed to resume it on a different client.**
 +
 +The fix this bug is to make X2Go Client behave like Linux or Mac clients. Therefore, a session started on X2Go Client for Windows 4.0.4.0 (or earlier) (under the conditions specified below) cannot be resumed on X2Go Client for Windows 4.0.5.0. However, a session started on X2Go Client for Windows 4.0.5.0 can be resumed on any client.
 +
 +The X2Go project therefore recommends that update all your Windows clients to 4.0.5.0 at the same time.
 +
 +To determine if a session cannot be resumed, open up a terminal in the session and run:
 +
 +<​code>​
 +xdpyinfo | grep -i StaticColor
 +</​code>​
 +If 1 line is outputted, then it cannot be resumed from those other clients. If no lines are outputted, then it can be.
 +
 +If all of the conditions are met, then a session started cannot be resumed on other clients:
 +  - You are using X2Go Client for Windows 4.0.4.0-2015.06.24 or prior.
 +  - OpenGL support is enabled in the Windows OS.
 +  - You are not accessing the Windows machine over Microsoft Remote Desktop Connection (which disables OpenGL support for the RDP session)
 +  - You started a Single App session, or a desktop session in windowed mode (Display: Custom) or "use whole display mode". (Every mode other than Fullscreen mode)
 +
 +Note that there are multiple reasons why OpenGL support may not be enabled in the Windows OS:
 +  * You have a graphics adapter that supports OpenGL, but the driver is not installed, or Windows provided a driver that supports Direct3D but not OpenGL
 +  * You are using a extremely-low-end dedicated server graphics adapter without OpenGL support
 +  * You are running Windows in a VM, on a hypervisor which does not support OpenGL (or where OpenGL is disabled)
 +
 +
 +
 +===== Available Builds =====
 +
 +There is only 1 build.
 +  * The regular build
 +
 +Both installers now include the regular build & the debug build of X2Go Client.
 +
 +==== Current Release ====
 +
 +The regular installer, x2goclient-4.0.5.0-2015.07.31-setup.exe , is available under this folder:
 +  * http://​code.x2go.org/​releases/​binary-win32/​x2goclient/​releases/​4.0.5.0-2015.07.31/​
 +
 +===== Supported Windows Versions =====
 +X2Go Client is currently only released as a 32-bit x86 build. Both 32-bit x86 and 64-bit x86 versions of Windows are supported via this build.
 +
 +  * Windows XP 32-bit SP3
 +  * Windows XP 64-bit SP2
 +  * Windows Vista SP2
 +  * Windows 7 SP1
 +  * Windows 8 
 +  * Windows 8.1 (with or without "​Update 1")
 +  * Windows 10 (RTM)
 +
 +These versions of Windows without the latest (specified) service pack may be compatible, but are rarely (if ever) tested. They are not officially supported.
 +
 +Corresponding server versions of Windows are also supported, but receive minimal testing:
 +  * Windows Server 2003 SP2
 +  * Windows Server 2003 R2 SP2
 +  * Windows Server 2008 SP2
 +  * Windows Server 2008 R2 SP1
 +  * Windows Server 2012
 +  * Windows Server 2012 R2 (with or without "​Update 1")
 +  * Windows Server Technical Preview
 +
 +Any incompatibility or bug with a specific version of Windows should be reported via our bug-tracker.
 +
 +===== Installation Instructions =====
 +See this page:
 +  * http://​wiki.x2go.org/​doku.php/​doc:​installation:​x2goclient
 +
 +===== Windows-Specific Bug Fixes =====
 +
 +[[http://​bugs.x2go.org/​cgi-bin/​bugreport.cgi?​bug=696|bug 696]] Can't resume session started by Windows X2Go client with Linux X2Go client
 +
 +[[http://​bugs.x2go.org/​cgi-bin/​bugreport.cgi?​bug=883|bug 883]] Window Decorations gone when resuming on smaller screen
 +
 +===== Noteworthy Windows-Specific Bugs =====
 +
 +[[http://​bugs.x2go.org/​cgi-bin/​bugreport.cgi?​bug=611|bug 611]] The server cannot be added to the known_hosts file (and thus you cannot connect to the server) when both of these conditions are met: 1. Your Windows username has non-English characters. 2 Those characters are in a different language than the Windows "​system locale"​.
doc/release-notes-mswin/x2goclient-4.0.5.0.txt ยท Last modified: 2015/07/31 13:18 by mikedep333