So I first tried reinstalling x2goclient and it did not work, even with an *apt-get purge* , deleting the *session* file in ~/.x2goclient/ and rebooting the server.

Then I finally noticed something :

• the connection did not work from my Laptop (which is of course, the one from which I need it to work) : Linux Mint 18 with x2go client 4.0.5
• the connection worked from an old Windows 7 with x2go client 4.1.1
• it also worked from a Debian 9 with x2go client 4.1.1

The version of x2go installed on the server is 4.1.0.

So it made sense to try installing the latest stable x2go client version. After checking, I ahd indeed not added the ppa to the software sources and was using the version from the Linux Mint repositories.

So I did that and now it works.

Shall I ask something to the wiki ?

Manfred A.

2018-03-15 15:54 GMT+01:00 Manfred Amoureux <mamoureux7@gmail.com>:

Ok.

Now that you have attracted my attention this git request ( *nxagent crashes when moving the session window into another screen* ), it actually looked more like a client-side issue, so I tested again from another computer (with Windows 7 and a single screen) and while at the first attempt the connection failed with a message that let me think it was because there was an open connection on the server with this user, after a reboot from the server machine, the connection now works from this computer.

So I guess it really is a client problem now. I am first going to to try uninstalling and reinstalling x2go client from my computer.

Manfred Amoureux Tel: (+33)6.800.343.16

2018-03-15 15:16 GMT+01:00 Mihai Moldovan <ionic@ionic.de>:

...

• On 03/15/2018 03:07 PM, Manfred Amoureux wrote:

...

I recorded a screen capture while trying to start a connection from another computer. See the link below. As you can see, it seems the connection gets opened but the window crashes immediately. I have tried from several computers (including one with Windows) so I don't think it's a problem on the client side.

Classic pattern of https://github.com/ArcticaProject/nx-libs/issues/677

Will be fixed with the next nx-libs release, but I cannot tell when that will be. Ideally I'd like to see more xinerama changes/fixes to make it worthwhile.

...

I have attached an extract of the /var/log/syslog file these last minutes. I see nothing that looks like an error to me. Obviously, you should be able to interpret it better than me. I have also restarted x2go (/sudo systemctl stop x2goserver.service/ and then /sudo systemctl start x2goserver.service/ ) after changing the /etc/x2go/x2goserver.conf file with logging to /debug/. That is the second text file attached.

In it, I can see : Mar 15 14:51:15 ServeurITeN /usr/bin/x2gostartagent: successfully started X2Go Agent session with ID manfred-50-1521121872_stDXFCE_dp24 Which means, I guess, the session was properly started.

Well, that message is an euphemism. We launched the binary, but everything that happens after that is unknown since we immediately put the process into background. But yeah, having it spawned nxagent is good.

...

However, further on, I can also see : Mar 15 14:51:22 ServeurITeN x2gogetstatus: db_getstatus called, session ID: manfred-50-1521121872_stDXFCE_dp24, return value: Mar 15 14:51:22 ServeurITeN x2gocleansessions: manfred-50-1521121872_stDXFCE_dp24: removed from database, not updating status. Mar 15 14:51:22 ServeurITeN x2gocleansessions: manfred-50-1521121872_stDXFCE_dp24: in failed state, but agent is gone, forgetting. Is that some kind of failure ?

That indicates that x2goagent/nxagent died after starting up.

...

It is also interesting to see that when I issue a /who/ command with the Linux Terminal , there is one extra session under my login.

Yup, X2Go uses SSH connections for everything.

...

So I tried opening a x2go session with another login, which also failed but with a different error message : "/Failed to start X2Go Agent session with ID formation-50-1521122343_stDXFCE_dp24. X2Go Agent terminated unexpectedly. Aborting session startup./" I then restarted the x2goserver.service again and tried again with the other user account and got the same error as for the first user ("The connection with the remote server was shut down. Please check the state of your network connection.").

The first error message is weird, but explainable by the fact that the proxy was not quick enough to connect in the first place (or something like this).

Right now, you have two options: wait for a new nx-libs release (as said, unspecified time) or switch to the nightly/heuler repository that contains a fix for this issue... and switch back to the stable version once the new version has been properly released.

Mihai