Mike Gabriel | 18 Jun 20:28 2013

Bug#192: X2Go issue (in src:python-x2go) has been marked as closed

close #192


we are very hopeful that X2Go issue #192 reported by you
has been resolved in the new release ( of the
X2Go source project »src:python-x2go«.

You can view the complete changelog entry of src:python-x2go (
below, and you can use the following link to view all the code changes
between this and the last release of src:python-x2go.


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:python-x2go.

Thanks a lot for contributing to X2Go!!!

X2Go Git Admin (on behalf of the sender of this mail)

X2Go Component: src:python-x2go
Date: Tue, 18 Jun 2013 20:27:42 +0200
Fixes: 192
 python-x2go ( RELEASED; urgency=low
   * New upstream version (
     - Save exports in session profile directly after mounting/unmounting a share
       if the session profile parameter restoreexports is set.
     - Fix the restoreexports logic on mount/unmount/unmount all requests.
       Make sure client-side offline network shares do not get purged from the
       session profile configuration if unavailable. (Fixes: #192).
     - Become aware of fixed paramiko features since paramiko 1.11.0. Stop
       monkey patching those methods that got fixed in 1.11.0.
     - Ignore KeyError exceptions in session cache for suddenly removed cache items.
       Silence/fix some race conditions on connection failures.
     - Support mounting client-side folders on UNC paths.
     - Enable keepalive callbacks on open SSH client connections.
     - Only do x2golistmounts calls for the session cache on running sessions.
     - Fix renaming of profile names.
X2Go-Dev mailing list
X2Go-Dev <at> lists.berlios.de