Subject: Bug#1016 closed by X2Go Release Manager <[email-masked]> (X2Go issue (in src:python-x2go) has been marked as closed)

From: [email-masked] (X2Go Bug Tracking System)
Date: Mon, 15 May 2017 14:40:03 +0000

This is an automatic notification regarding your Bug report
which was filed against the python-x2go package:

#1016: python-x2go breaks with gevent 1.1.0

It has been closed by X2Go Release Manager <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact X2Go Release Manager <[email-masked]> by
replying to this email.

-- 
X2Go Bug Tracking System
Contact [email-masked] with problems

Subject: X2Go issue (in src:python-x2go) has been marked as closed
From: X2Go Release Manager <[email-masked]>
To: [email-masked]
Cc: [email-masked], [email-masked]
Date: Mon, 15 May 2017 16:39:35 +0200 (CEST)

close #1016
thanks

Hello,

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

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

    http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=64c77967e7ae4ec038549eb19fef5c6fc5b525af;hp=59e42be74d34033dfd259bcfc54a84399893c44b

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!!!

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

---
X2Go Component: src:python-x2go
Version: 0.5.0.5-0x2go1
Status: RELEASE
Date: Mon, 15 May 2017 16:38:16 +0200
Fixes: 1016
Changes:
 python-x2go (0.5.0.5-0x2go1) RELEASED; urgency=low
 .
   [ Mike Gabriel ]
   * New upstream version (0.5.0.5):
     - documentation: Fix wording in docstring.
     - Don't blindly release gevent locks. We need to check if a
       semaphore is locked for some code paths and only then release it.
       (Fixes: #1016).
 .
   [ Mihai Moldovan ]
   * New upstream version (0.5.0.5):
     - x2go/__init__.py: update mailing list address.
   * debian/control:
     - Maintainer change in package: X2Go Developers <[email-masked]>.
     - Uploaders: add myself. Also, force a rebuild due to the changed
       versioning.

Subject: python-x2go breaks with gevent 1.1.0
From: Cezary Statkiewicz <[email-masked]>
To: [email-masked]
Date: Fri, 01 Apr 2016 19:27:59 +0200

Package: python-x2go
Version: 0.5.0.4

 Hi,

 I'm using x2go python bindings, and noticed that X2GoSession's .suspend() can 
break with gevent 1.1. I've downgraded gevent to 1.0.2 and unchanged code 
works fine with it.

 Sample code (i believe taken from a sample code):

 class Client(X2GoClient):
    def do_connect(self):
        ...
        sid = self.register_session(server=session_args.pop('server', None),
                                    username=session_args.pop('username', 
None),
                                    profile_name=session_args.pop('profile_name', 
None),
                                    port=session_args.pop('port', None),
                                    return_object=True)
        sid.update_params(session_args)
        sid.connect()
        self.clean_sessions(sid.uuid)
        sid.start(cmd='XFCE')

        session_name = sid.get_session_name()
        if session_name is None:
            log.error("X2Go session creation: Session name is None, 
terminating")
            return
        sid.suspend()
        ...

 Traceback:

  File "/usr/lib/python2.7/dist-packages/x2go/session.py", line 2303, in 
suspend
    self._lock.release()
  File "gevent/_semaphore.py", line 266, in 
gevent._semaphore.BoundedSemaphore.release (gevent/gevent._semaphore.c:4866)
  File "gevent/_semaphore.py", line 268, in 
gevent._semaphore.BoundedSemaphore.release (gevent/gevent._semaphore.c:4802)
thread.error: Semaphore released too many times

 Best Regards,

 Cezary Statkiewicz