[X2Go-Dev] Bug#137: The reported issue has been fixed in X2Go Client 4.0.1.0