close #471 thanks
Hello,
we are very hopeful that X2Go issue #471 reported by you has been resolved in the new release (4.0.1.15) of the X2Go source project »src:x2goserver«.
You can view the complete changelog entry of src:x2goserver (4.0.1.15) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver.
http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=7e43e787a8ffe26a34b66dbd4dc167e4cf29f74c;hp=ed4a76ce5015ee195476d2612abc94459e552c3a
If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver.
Thanks a lot for contributing to X2Go!!!
light+love X2Go Git Admin (on behalf of the sender of this mail)
X2Go Component: src:x2goserver Version: 4.0.1.15-0x2go1 Status: RELEASE Date: Thu, 03 Apr 2014 11:35:50 +0200 Fixes: 471 Changes: x2goserver (4.0.1.15-0x2go1) RELEASED; urgency=low .
Processing commands for control@bugs.x2go.org:
close #471 Bug #471 [x2goserver] ATTENTION @Mike#1 - serious bug in x2goserver upgrade script (debian wheezy+squeeze) Marked Bug as done thanks Stopping processing here.
471: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=471 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems