Yes deleting /tmp/.x2go-$USER did fix it. It happens rarely. I'm not sure how long the session runs before this occurs. A fix for this issue would be great. Thanks for the suggestion!
On Sat, 18 Nov 2017, Mihai Moldovan wrote:
- On 11/18/2017 09:32 AM, Andrew Munn wrote:
Sometimes x2go works fine. Other times I can't get the session back and logs look like this. server version 4.0.1.20. Same results occur when connecting from my Windows or Linux client.
Might that be the same problem as described by the other user - i.e., something deleting files in /tmp/, which stores the session data?
Does that problem only happen after the session has been created for a while?
Mihai