After upgrading to net-misc/nxserver-freenx-0.5.0-r1, when I logoff from an nxsession (specifically from kde 3.5, but I don't think that is the issue) the logoff proceeds properly, but the nxsession is never cleared and when I connect the next time, it first tries to start the closed session before giving an error message. The next time I connect it would then start a fresh session. After logging off, I still notice that there is a sessionid in /var/lib/nxserver/db/running. If I run nxserver --cleanup then I will receive the following error message on the client; "The connection with the remote server was shut down. Please check the state of your network connection."
please dont use bugzilla for support requests
Hi SI, I've noticed the same problem with GNOME. I don't yet know what's causing it, but it's annoying as hell. I won't be stabilising nxserver-freenx until this has been solved. Best regards, Stu
Hi ebfe, I don't know who you are, but please don't tell other Gentoo users how they should or should not be using our Bugzilla system. Best regards, Stu
I can get it to exit cleanly when I change the following line in /etc/nxserver/node.conf: ENABLE_2_0_0_BACKEND="0" I am using a 1.5 client
Looking at nxnode the variable ENABLE_2_0_0_BACKEND must be set to 1 only if nxagent is version >= 2.0; So, since net-misc/nx installs nxagent version 1.5, that variable has to be forced = 0. To enable client connections with client version >= 2.0 and backend version = 1.5, nxnode has to be modified to handle correctly the "backingstore" parameter.
Created attachment 102459 [details, diff] nx 1.5 backend and client 1.5 and 2.0 fix
Changing bug state.
Thanks, nxserver-freenx-0.5-r2 in CVS Now, you can also use the recently added nxserver-freenx-0.6
