freenx-team team mailing list archive

[Marcelo Boveto Shima <marceloshima@xxxxxxxxx>]

You are running intrepid?

On Wed, Sep 10, 2008 at 11:08 AM, TH <tino.hirschmann@xxxxxxxxxxxxx>
wrote:

> I pruged the FreeNX packages and reinstalled. However both problems
> persist.
> NXserver also still does not correctly clean up old sessions ...
>
> ck-list-session shows the following:
> Session3:
>        uid = '1000'
>        realname = 'th,,,'
>        seat = 'Seat4'
>        session-type = 'python'
>        active = FALSE
>        x11-display = ':1000'
>        x11-display-device = ''
>        display-device = ''
>        remote-host-name = ''
>        is-local = TRUE
>        on-since = '2008-09-10T14:02:54Z'
> Session1:
>        uid = '1000'
>        realname = 'th,,,'
>        seat = 'Seat2'
>        session-type = ''
>        active = TRUE
>        x11-display = 'localhost:10.0'
>        x11-display-device = ''
>        display-device = '/dev/pts/0'
>        remote-host-name = '10.XX.XX.XX'
>        is-local = FALSE
>        on-since = '2008-09-10T13:53:36Z'
> Session2:
>        uid = '1000'
>        realname = 'th,,,'
>        seat = 'Seat3'
>        session-type = 'nx'
>        active = TRUE
>        x11-display = ':1000'
>        x11-display-device = ''
>        display-device = ''
>        remote-host-name = ''
>        is-local = TRUE
>        on-since = '2008-09-10T14:02:53Z'
>
> --
> 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?
>
> _______________________________________________
> Mailing list: https://launchpad.net/~freenx-team<https://launchpad.net/%7Efreenx-team>
> Post to     : freenx-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~freenx-team<https://launchpad.net/%7Efreenx-team>
> More help   : https://help.launchpad.net/ListHelp
>

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