[FreeNX-kNX] Rootless mode suspend

[Terje Andersen]

I have followed your solution/workaround and have gotten something of 
the same results, Ed.

>Ed Warnicke wrote:
>
>  
>
>>Upon even further reflection I suspect the issue
>>is an incompatibilty with the new nxclient-1.5.0.
>>    
>>
I have the same feeling here - the problems started when I upgraded to 
the 1.5.0 client. I found a WinXP client that I hadn't upgraded the 
client to 1.5.0 yet, and when not using the your workaround within 
nxnode, I could actually connect as usual to the FreeNX 0.4.2 running 
nxlibs 1.5.0 (release) again.

>>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?
>>    
>>
Looks like this at my setup too, but it's some small differences;

on the client running 1.5.0 when clicking on details, I get (I've 
attached an image with several sessions):

Session Name = <blank>
Type = ander 10.1.1.24
Geometry = x
Status = <blank>
Services = 65504187DADAB81EA
Display = 1000 te

On the server it looks like this:

compaq:/usr/NX/bin# ./nxserver --list
NX> 100 NXSERVER - Version 1.4.0-05-SVN OS (GPL)
NX> 127 Sessions list:

Display Username        Remote IP       Session ID
------- --------------- --------------- --------------------------------
1000    terander        10.1.1.248      6A91C2304FD804965504187DADAB81EA
NX> 999 Bye

Looks like the fields have shifted - this would mean to me that one of 
the fields are either wrongfully interpreted, or that one of the fields 
from the new client are longer than expected in the previous client.

>>Also, is nxclient-1.5.0 incompatible with older listsession formats
>>(and thus older servers)?
>>    
>>
don't know, but sure looks like it, though.

>>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.
>>>      
>>>
I have the same results here, too.

>>>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.
>>>      
>>>
I upgraded the nxlibs on one of the servers, and then upgraded the 
client at the same time. This made me look at the server as the possible 
source for the problem, but I get the same results connecting to the 
other server with snapshot2 nxlibs, which leads me to believe that it 
isn't the nxlibs that is the problem, but the interpretation of the new 
nxclient when using the new 1.5.0 protocol (if I have understood things 
correctly....  :-) )
The workaround you mentioned got me one step further - I at least got a 
connection which then fails when I choose to create a new session - 
resuming doesn't work either.

>>>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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nxsessions.JPG
Type: image/jpeg
Size: 21775 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20050724/9f36a223/attachment.jpe>