Summary:
1. I did need to terminate/restart.  Now I see sleep=0 in options
2. I could see processes are sleeping by ssh into machine: when x2go was active I had a bunch
of processes running 100%, then when suspended they are not active.
3. Remaining mystery is why I have other older installations that never did this, but this new machine sleeps by default.  
    The older installs, also Fedora, have all been kept up-to-date.

On Wed, Feb 12, 2020 at 3:04 AM Ulrich Sibiller <uli42@gmx.de> wrote:
On Wed, Feb 12, 2020 at 2:10 AM Neal Becker <ndbecker2@gmail.com> wrote:
>
> I've used x2go on linux (Fedora) for years and never experienced this before.  I just setup a new workstation.
> When I suspend a session, the running processes started by it seem to sleep.  A bit of googling suggested I
> need to edit /etc/x2go/x2goagent.options setting:
> X2GO_NXOPTIONS="sleep=0"
>
> I hope this helps: it hasn't yet.  Will this only take effect after I terminate the current session and start a new one?

Well, nx-wise (nx is the underlying technology) the option is read at
startup or resume.

I am not sure if x2go is reading the option on resume, too, to pass it
down to nx. I'd need to check this.

If you run on suspend/resume cycle after adding the option you can
check if it has reached the nx layer by checking the options file in
~/.x2go/<session>/options. If the sleep option is visible there and
still not working you have hit an nx bug.

Uli

BTW: how do you determine if you apps are sleeping?


--
Those who don't understand recursion are doomed to repeat it