[FreeNX-kNX] suspend does not work

[Fabian Franz]

Am Mittwoch, 13. Oktober 2004 12:17 schrieb Markus Kremer:
> Hi,
> i am using FreeNX 0.2.4 and nx 1.4.0. 

Which snapshots? This is quite important, as the format has changed from 
snapshot 4 to 5/6 and so a reconncetion with different snapshots does not 
work in all cases.

> The server uses suse 8.2 and the
> client is  a w2k pc with the 1.4 client from nomachine. 

Again, which one exactly?

> The windowmanager
> is icewm. (replaced startkde call)
>
> When i try to close the client window nothing happens.

Interesting. You don't have any nxclient installed on the server, neither by 
freenx nor by nomachine?!

> when i do nxserver --suspend USERNAME the client window closes and i get:
>
> # nxserver --suspend USERNAME
> # nxserver -list
> NX> 100 NXSERVER - Version 1.4.0-02 OS_(GPL)
> NX> 127 Sessions list:
>
> Display Username        Remote IP       Session ID
> ------- --------------- --------------- --------------------------------
> 1006    USERNAME 123.4.5.6     7F964E8B5CA0A65BD8AA43BF470D9C81
> NX> 999 Bye

> # nxserver --list-suspended
> NX> 100 NXSERVER - Version 1.4.0-02 OS_(GPL)
> NX> 999 Bye

Wrong syntax. Right is:

# nxserver --list-suspended USERNAME
>
> The NX session administrator reports session closed.
> when i try to start nxclient, it does a reconnect, says "Established X
> server connection". The session window appears for a fraction of a second
> and closes again.

Yes, this seems like a problem with mixed snapshots. You might see an error 
message in the client with [N] or similar.

>
> Then i have to do nxserver --terminate USERNAME in order to get a new
> session.

You can also just rename the session in nxclient to get a new one ...
>
> Whats wrong / how can i dig deeper?

Seems like mixing-of-snapshots problem as outlined above.

cu

Fabian