[X2Go-Dev] Bug#100: This issue has been solved in X2Go Client 4.0.0.2