[FreeNX-kNX] Problem Resuming Session

[Jack Tanner]

Perhaps I should elaborate. :)

I've been plagued with this problem: I use the latest NM Windows client 
to connect to Freenx on FC4 (running Rick Stout's latest RPMs). No 
matter the init script tricks, gnome-session would not run. I think I 
posted my session file at some point, which contained errors like 
"nxagent didn't recognize parameter X..." for a bunch of parameters that 
should be set by the client.

So, on a whim, while logged into my FC4 box over ssh (not through NX), I 
did $ rm -rf ~/.nx. (If you do it while being logged in via NX, it will 
undoubtedly cause problems for your NX session.)

Since then, however, I've used the same NX client to log into the same 
FC4 box with the same installation of Freenx, and, lo and behold, 
gnome-session runs, and suspend works.

So, from now on, when upgrading either the Windows client or the 
Freenx/NM components, I'm going to rm ~/.nx, and I strongly encourage 
others who run into silly, hard to reproduce problems to try the same.

Nick wrote:
> Not exactly sure what that's meant to achieve but when I tried it a new 
> session was started instead of being resumed. I guess that's because the 
> session info was stored in ~.nx/ !!
> 
> Nomachine don't give out older versions of clients and I can't really 
> blame them. After all, if freenx worked as well as the official server 
> no one would buy it! So unless you can find an older client or freenx 
> gets fixed I guess you'll have to do without resuming from Windows :o(
> 
> Jack Tanner wrote:
> 
>> OMG. I may have stumbled upon a ridiculously simple solution to this 
>> problem.
>>
>> $ rm -rf ~/.nx
>>  
>>