X2Go Bug report logs - #1406
connection failed after an update of nxagent on differents servers debian 10

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: ELODIE TOSETTO <elodie.tosetto@univ-grenoble-alpes.fr>

To: submit <submit@bugs.x2go.org>

Subject: connection failed after an update of nxagent on differents servers debian 10

Date: Wed, 18 Sep 2019 09:19:05 +0200 (CEST)

[Message part 1 (text/plain, inline)]

Package: x2goserver 
Version:  4.1.0.3-4 

Hi, 

We are experiencing a connection problem via x2go on our recently updated servers.
The update that seems to have initiated the problem impacted nxagent, nxproxy, libnx-x11-6,
nx-x11-common 


- client side we have this error:
The connection failed. Unable to start X2Go Agent session with ID
XXXXXX-50-1568727595_stRTERMINAL_dp24. Agent X2Go completed
unexpectedly. Aborting the start of the session

- on the server side we have these details
Sep 17 15:57:31 ist-debian / usr / bin / x2gostartagent: successfully started
X2Go Agent Session with ID XXXXXXX-50-1568728649_stRTERMINAL_dp24

Other ssh clients like MobaXterm or putty are working properly. 
On servers where we have no recent update but are also in debian 10 we have no problem. 

We use Debian Debian GNU / Linux 10 \ n \ l 
after the problematic update, the version of the agent nx is 
ii nxagent 2:3.5.99.19-3+deb10u1 


Thanks for your help 

Elodie TOSETTO 
laboratoire ISTerre/UGA 
Service informatique 
Maison des Géosciences 
OSUG C 
1381 rue de la piscine 
38400 St Martin d'Hères 
tel [+33][0]4-76-63-52-22 
www.isterre.fr 

[Message part 2 (text/html, inline)]

Message #10 received at 1406@bugs.x2go.org (full text, mbox, reply):

From: ELODIE TOSETTO <elodie.tosetto@univ-grenoble-alpes.fr>

To: 1406@bugs.x2go.org

Date: Thu, 19 Sep 2019 16:39:58 +0200 (CEST)

[Message part 1 (text/plain, inline)]

This bug has been solved by debian. 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940104 

the package nxagent 2:3.5.99.19-3+deb10u2 is correcting the problem. 

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.