[FreeNX-kNX] Rootless mode suspend

Terje Andersen terander at guard.zapto.org
Sun Jul 24 20:41:58 UTC 2005


Ed Warnicke wrote:

>Upon even further reflection I suspect the issue
>is an incompatibilty with the new nxclient-1.5.0.
>
>I notice this when I downgraded to freenx-0.4.0
>and nx-1.4.0, created a session, suspended the
>session, and then reconnected the nxclient
>brought up the "Available sessions" dialog.
>In showed my session, but the fields where
>all screwed up:
>
>"Session Name" is blank.
>"Type" is "10.83.44.67 F7"
>"Geometry" is "x"
>"Status" is blank.
>"Services" is "63586179AFF20"
>"Display" is "1002 ea"
>
>If you compare this to the data from the
>nxserver.log:
>
>NX> 105 listsession --user="eaw" --status="suspended,running" 
>--geometry="1600x1200x24+render" --type="unix-kde"
>NX> 127 Sessions list of user 'eaw'
>
>Display Username        Remote IP       Session ID
>------- --------------- --------------- --------------------------------
>1002    eaw     10.83.44.67     F7AB4DA898D6EEACAF863586179AFF20
>
>You can see that it's getting it's data from this listing, but
>that it's misattributing fields.  Has the expected output from
>listsessions shifted, and if so, what can be done about it?
>
>Also, is nxclient-1.5.0 incompatible with older listsession formats
>(and thus older servers)?
>
>Ed
>
>Ed Warnicke wrote:
>
>  
>
>>Upon further investigation, while I can get
>>full desktop sessions to suspend (using FreeNX 0.4.2
>>and nx-1.5.0) I can't resume them.  When I attempt
>>to connect they are displayed, but the nxclient
>>"Resume" button is greyed out.  Termination of
>>sessions from the nxclient also doesn't seem to
>>work.
>>
>>The reasons I mention these issues is because
>>I'm wondering if it's related to a change I had
>>to make to get nx-1.5.0 working at all.
>>
>>FreeNX 0.4.2 worked fine for me with the old
>>nx-1.4.0 libs.  When I upgraded to nx-1.5.0
>>I could not get a successful connection.  It
>>kept dying during 'Establishing X connection'
>>and giving a Warning about mismatched cookies.
>>Finally in desperation I tried setting
>>$proxy_cookie=$cookie in nxnode, and then
>>I could get working sessions.
>>
>>Thoughts or suggestions?
>>
>>Ed
>>Ed Warnicke wrote:
>>
Sorry, Ed, but I have no solution to your problem, but I'll have to say 
thank you for your solution in nxnode, because I'm having excactly the 
same problem as you!
I have two test-servers; one running nxlibs 1.5.0 (snapshot 2)  & FreeNX 
0.4.2 and one running nxlibs 1.5.0  (release) & FreeNX 0.4.2. After I 
upgraded the client to 1.5.0 I couldn't connect to any one of them.
I'll try your solution and see if that lets me connect to the servers again.

/Terje




More information about the FreeNX-kNX mailing list