On 05.03.2015 10:29 PM, Les Mikesell wrote:
Don't you run into trouble with applications clobbering their own hidden files or things like firefox launching what you expected to be a new instance as a window in one of the suspended sessions instead? And when reconnecting, how do you distinguish which session you want?
I do not. But this is merely because I am not starting multiple desktop sessions at a time or applications that do not support concurrency, but "plain" stuff like xterms or the like.
I'll give an example:
Currently, I have a session running on my server for "video editing" purposes. This session is rootless and consists of 3 xterms, from which I start a video player (mpv) every now and then or edit text files or move stuff around. I do not want to use this session but merely for this "video editing".
This said, when working on x2goclient or x2goserver, I have to start a new session quite often. Maybe because some issue I'm looking into is dependent on x2goserver's or x2goclient's behavior *when starting a session* or because I have to explicitly test a non-rootless mode (like custom desktop via fluxbox.)
I also have another session with xterms and an application running exclusively for some other, undisclosed purpose.
For my use case, I want the terminals and applications to be independent from each other and I don't really use a desktop session or browser regularly.
This use case is totally different from your thinclient-like use case. And that's fine. You want integration, I want isolation. X2Go is supposed to support both. We really try to satisfy all reasonable/generic use cases.
Mihai