I have found this not only happens with x2go but also with nx and vnc
and I believe it has to do with systemd sessions.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 19 Jan 2018, Ulrich Sibiller wrote:
Date: Fri, 19 Jan 2018 21:20:10 +0100 From: Ulrich Sibiller <uli42@gmx.de> To: Robert Dinse <nanook@eskimo.com> Cc: RW <garlicbready@googlemail.com>, x2go users <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2go local desktop connection on rpi
On Fri, Jan 19, 2018 at 3:45 PM, Robert Dinse <nanook@eskimo.com> wrote:
This is I think an issue with Ubuntu, it won't allow two graphical
logins from same user on same machine, but if you originate with a different UID than you connect with it is okay.
The relevant information is probably in the server side session log (/tmp/.x2go-<username>/C-<username>-<displaynum>.*/session.log. You should find the reason why the connect did fail.
I would also suggest switching to nx 3.5.99.13 which offers the tolerancechecks (see man nxagent) option to make reconnects possible where 3.5.0 simply does not allow them. Here's how: https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
You'd have to suspend your session, then edit /tmp/.x2go-<username>/C-<username>../options (add the tolerancechecks=<yourvalue> option), then try to reconnect.
Uli