freenx-team team mailing list archive

[TH <tino.hirschmann@xxxxxxxxxxxxx>]

Tried that. However with this setting I am no longer able to log in,
since the SSH Daemon only accepts public key based authentication, which
can not be changed. Besides that I also noticed that with the latest
0.7.3 freenxteam version "Unlocking" of PolicyKit based items does not
longer work for me. The nx-session-launcher-suid is also no longer set
suid, is this by intention? Anway, changing that will not resolve the
problem and will no longer allow any nx logins. In addition old session
are not correctly remove from the session list even so they are
correctly closed by the client.

I switched back to 0.7.2+svn544-0freenxteam6, which does not show any
problems at all. Both suspend/resume as well as "Unlocking" works like a
charm.

So the question remains what causes this problems and how can this be
fixed?

-- 
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?