freenx-team team mailing list archive

[Marcelo Boveto Shima <marceloshima@xxxxxxxxx>]

There is a bug in nx-session-launcher. Should be fixed in freenxteam7.
Looks like this bug makes freenx don't cleanup the session.
Unlock problem should really be fixed.

Can you try suspending in this new version?
Execute "$/etc/init.d/freenx-server restart" after upgrade.
This will cleanup the sessions.

-- 
Suspend/Resume not working
https://bugs.launchpad.net/bugs/268197
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New

Bug description:
Since upgrading to the freenx-team freenx version I am not longer able to resume a suspended session. Reconnecting to a server will always result in a new nx session. I therefore have to remove old session manually with nxserver --cleanup.
I am using the latest nx client versions from nomachine for mac os x and windows (3.2.0-13). 

I attached my nxserver node.conf to show you my current configuration. I am only using su authentication since this works best in our current scenario.

Any idea how I could resolve this problem?