On Mon, Feb 06, 2023 at 09:18:22PM +0100, Ulrich Sibiller wrote:
In case you close your laptop the network connection will go down. The x2goagent will notice after some time that the other side (the laptop) is not answering/sending data anymore and will detect a DISPLAY failure (since the remote X server is not available anymore) and suspend the session.
If you have configured sleep=0 then your applications (meaning Xclients running on the server side, connecting to the x2goagent) will not notice any change as the x2goagent is still there, otherwise they will be slowed down until x2goagent is woken up again by an x2goclient that wants to connect.
But that's where I notice a difference. If I disconnect the x2go session cleanly, either using the "stop" button or just closing the window, things work as you described. If I don't close the session cleanly, e.g. by just sending the laptop to sleep, or by kill -9 on the x2go client, the remote session stops as if I didn't configure sleep=0.
I'm not entirely sure if it's always the case, but quite often at least, and certainly today when I tested again. And I don't remember that behaviour from years ago, but that's probably just me.
Hanno