[FreeNX-kNX] Re: nxnode floating point exception

[Jeff Siddall]

On 11/05/2010 06:24 AM, chris at ccburton.com wrote:
> [SNIP]
>> My only remaining question is whether suspending a session generally a
>> bad thing?  Any ideas why my suspended session broke future connection
>> attempts?
> 
> We experience a number of issues with resuming suspended sessions,
> mostly to do with reconecting from a different workstation and linked to
> screen size or windows/linux.
> 
> The user expects to re-connect but gets a new session.
> 
> Sometimes a user just gets a new session when they want to
>  reconnect, even from the same machine.
> 
> Sometimes a session doesn't terminate properly and some files remain
> locked until we clean up old nxagent instances.
> 
> Sometimes a user hoping for a second session finds they take over
> their first session and don't get the option to start a second session.
> 
> On the whole it is reliable enough in our experience, but we have
> to be available just in case.
> 
> Suspended sessions are v useful for running big reports or for
> people on the move . . .

SOLVED!

Session resume was really broken for me -- as in it _never_ worked, even
from the same machine with all the same settings.

I discovered by chance that checking the "disable encryption of all
traffic", which I used because I was running over OpenVPN already
anyway, completely breaks session resume even though you can start a
session with that box checked.

Re-enabling compression resulted in reliable resumes.

Is this a known issue?  I really don't need two levels of encryption.

Next issue is sound... :(

Jeff