From unknown Sun May 17 03:42:38 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#583: Solved - problem in my application Reply-To: "Hanak" , 583@bugs.x2go.org Resent-From: "Hanak" Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Wed, 22 Oct 2014 10:05:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 583 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 583-submit@bugs.x2go.org id=B583.141397222023137 (code B ref 583); Wed, 22 Oct 2014 10:05:01 +0000 Received: (at 583) by bugs.x2go.org; 22 Oct 2014 10:03:40 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=ham version=3.3.2 X-Greylist: delayed 399 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Wed, 22 Oct 2014 12:03:39 CEST Received: from ngfw3.officehouse.cz (ngfw3.officehouse.cz [62.209.199.98]) by ymir.das-netzwerkteam.de (Postfix) with SMTP id D792E5DB49 for <583@bugs.x2go.org>; Wed, 22 Oct 2014 12:03:39 +0200 (CEST) Received: (qmail 7327 invoked from network); 22 Oct 2014 11:56:58 +0200 Received: from unknown (HELO alfik.amazon.xx) (10.168.7.91) by imap-ha.edison.xx with SMTP; 22 Oct 2014 11:56:58 +0200 Received: from hanak by alfik.amazon.xx with local (Exim 4.80) (envelope-from ) id 1Xgsf4-0000XT-KV for 583@bugs.x2go.org; Wed, 22 Oct 2014 11:56:58 +0200 From: "Hanak" To: 583@bugs.x2go.org Date: Wed, 22 Oct 2014 11:56:58 +0200 Message-ID: <83k33sbf6d.fsf@alfik.amazon.xx> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Hi, yesterday I discover a bug in my application which caused the problem! We were used to start the application from nxclient since ages and I completely forgot, that there was some very old "cleaning" procedure which was actually trying to solve some problems with nxclient stalled sessions. This "cleaning" procedure couldn't coexist with the different approach x2goclient, which caused closing of x2go sessions after some time of inactivity. Thanks a lot for all your help a I apologize for any disturbance. Good thing is that I could learn much more about how x2go works... The bug 583 can be considered as closed. Pavel