[lucid] [regression] Session resume not working anymore

Forgot to mention: I've purged all NX related packages, deleted [1] and [2] and reinstalled freenx - no success.

[1] /usr/share/freenx-server
[2] /var/lib/nxserver

Have you used aptitude to remove?
when adding the repos make sure that you modify then to karmic and install
again

2010/6/4 Markus Schuster <email address hidden>

> Forgot to mention: I've purged all NX related packages, deleted [1] and
> [2] and reinstalled freenx - no success.
>
> [1] /usr/share/freenx-server
> [2] /var/lib/nxserver
>
> --
> [lucid] [regression] Session resume not working anymore
> https://bugs.launchpad.net/bugs/589723
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>
> Status in FreeNX open source NX Server: New
>
> Bug description:
> I've upgraded from karmic to lucid these days and also upgraded freenx to
> 0.7.3.git100327.e224628-0~ppa4~lucid1.
>
> Now I'm unable to resume a previously suspended session - worked without
> any problems in karmic.
>
> Here's what the "session" file says:
> [..]
> Session: Suspending session at 'Fri Jun 4 16:47:01 2010'.
> Info: Waiting the cleanup timeout to complete.
> Session: Session suspended at 'Fri Jun 4 16:47:11 2010'.
> Session: Resuming session at 'Fri Jun 4 16:48:47 2010'.
> Info: Proxy running in server mode with pid '8524'.
> Info: Waiting for connection from '127.0.0.1' on port '6000'.
> Info: Aborting the procedure due to signal '15'.
> Session: Display failure detected at 'Fri Jun 4 16:48:47 2010'.
> Session: Suspending session at 'Fri Jun 4 16:48:47 2010'.
> Session: Session suspended at 'Fri Jun 4 16:48:47 2010'.
>
>
> That's what the Nomachine NX client tells me:
> NX> 203 NXSSH running with pid: 2908
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: XXXXXXXXX on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
> NX> 105 hello NXCLIENT - Version 3.2.0
> NX> 134 Accepted protocol: 3.2.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: markus
> NX> 102 Password:
> NX> 103 Welcome to: terminalserver user: markus
> NX> 105 listsession --user="markus" --status="suspended,running"
> --geometry="1280x1024x32+render" --type="unix-kde"
> NX> 127 Sessions list of user 'markus' for reconnect:
>
> Display Type Session ID Options Depth
> Screen Status Session Name
> ------- ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
> 2000 unix-kde D7E1A5D627ED20667867EBBB74C88FCB -RD--PSA 32
> 1274x962 Suspended XXXXXXXX
>
>
> NX> 148 Server capacity: not reached for user: markus
> NX> 105 restoresession --link="adsl" --backingstore="1" --encryption="1"
> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
> --composite="1" --media="0" --session="XXXXXXXXXXXXX" --type="unix-kde"
> --geometry="1274x962" --client="winnt" --keyboard="pc102/de"
> --id="D7E1A5D627ED20667867EBBB74C88FCB" --resize="1"
>
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
> NX> 105 /usr/bin/nxse...

> Have you used aptitude to remove?

Yes.

> when adding the repos make sure that you modify then to karmic and install
> again

Did so and now suspend and resume works fine again. But well... I expected
this, as the karmic version has worked flawlessly in the past. There is some
sort of bug in the version in the lucid repo and I think is should be hunted
down...

:) yes it should FreeNX rocks !!

2010/6/4 Markus Schuster <email address hidden>

> > Have you used aptitude to remove?
>
> Yes.
>
>
> > when adding the repos make sure that you modify then to karmic and
> install
> > again
>
> Did so and now suspend and resume works fine again. But well... I expected
> this, as the karmic version has worked flawlessly in the past. There is
> some
> sort of bug in the version in the lucid repo and I think is should be
> hunted
> down...
>
> --
> [lucid] [regression] Session resume not working anymore
> https://bugs.launchpad.net/bugs/589723
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>
> Status in FreeNX open source NX Server: New
>
> Bug description:
> I've upgraded from karmic to lucid these days and also upgraded freenx to
> 0.7.3.git100327.e224628-0~ppa4~lucid1.
>
> Now I'm unable to resume a previously suspended session - worked without
> any problems in karmic.
>
> Here's what the "session" file says:
> [..]
> Session: Suspending session at 'Fri Jun 4 16:47:01 2010'.
> Info: Waiting the cleanup timeout to complete.
> Session: Session suspended at 'Fri Jun 4 16:47:11 2010'.
> Session: Resuming session at 'Fri Jun 4 16:48:47 2010'.
> Info: Proxy running in server mode with pid '8524'.
> Info: Waiting for connection from '127.0.0.1' on port '6000'.
> Info: Aborting the procedure due to signal '15'.
> Session: Display failure detected at 'Fri Jun 4 16:48:47 2010'.
> Session: Suspending session at 'Fri Jun 4 16:48:47 2010'.
> Session: Session suspended at 'Fri Jun 4 16:48:47 2010'.
>
>
> That's what the Nomachine NX client tells me:
> NX> 203 NXSSH running with pid: 2908
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: XXXXXXXXX on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
> NX> 105 hello NXCLIENT - Version 3.2.0
> NX> 134 Accepted protocol: 3.2.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: markus
> NX> 102 Password:
> NX> 103 Welcome to: terminalserver user: markus
> NX> 105 listsession --user="markus" --status="suspended,running"
> --geometry="1280x1024x32+render" --type="unix-kde"
> NX> 127 Sessions list of user 'markus' for reconnect:
>
> Display Type Session ID Options Depth
> Screen Status Session Name
> ------- ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
> 2000 unix-kde D7E1A5D627ED20667867EBBB74C88FCB -RD--PSA 32
> 1274x962 Suspended XXXXXXXX
>
>
> NX> 148 Server capacity: not reached for user: markus
> NX> 105 restoresession --link="adsl" --backingstore="1" --encryption="1"
> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
> --composite="1" --media="0" --session="XXXXXXXXXXXXX" --type="unix-kde"
> --geometry="1274x962" --client="winnt" --keyboard="pc102/de"
> --id="D7E1A5...

Experienced the same problem:
Used following workaround:
1. sudo bash
2. aptitude remove freenx
3. apt-get install neatx-server
4. Ctrl+D

Now reconnect works fine.

Tried Neatx, worked fine but not as fast and I knew how to configure
FreeNX. How was configuring neatx for you?
Lewis

On Tue, Jun 8, 2010 at 7:45 AM, Meldo <email address hidden> wrote:

> Experienced the same problem:
> Used following workaround:
> 1. sudo bash
> 2. aptitude remove freenx
> 3. apt-get install neatx-server
> 4. Ctrl+D
>
> Now reconnect works fine.
>
> --
> [lucid] [regression] Session resume not working anymore
> https://bugs.launchpad.net/bugs/589723
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>

neatx for me is slower and stops working after some time of use. I prefer
FreeNX

2010/6/8 ludovicus <email address hidden>

> Tried Neatx, worked fine but not as fast and I knew how to configure
> FreeNX. How was configuring neatx for you?
> Lewis
>
>
> On Tue, Jun 8, 2010 at 7:45 AM, Meldo <email address hidden> wrote:
>
> > Experienced the same problem:
> > Used following workaround:
> > 1. sudo bash
> > 2. aptitude remove freenx
> > 3. apt-get install neatx-server
> > 4. Ctrl+D
> >
> > Now reconnect works fine.
> >
> > --
> > [lucid] [regression] Session resume not working anymore
> > https://bugs.launchpad.net/bugs/589723
> > You received this bug notification because you are a member of FreeNX
> > Team, which is the registrant for FreeNX Server.
> >
>
> --
> [lucid] [regression] Session resume not working anymore
> https://bugs.launchpad.net/bugs/589723
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>
> Status in FreeNX open source NX Server: New
>
> Bug description:
> I've upgraded from karmic to lucid these days and also upgraded freenx to
> 0.7.3.git100327.e224628-0~ppa4~lucid1.
>
> Now I'm unable to resume a previously suspended session - worked without
> any problems in karmic.
>
> Here's what the "session" file says:
> [..]
> Session: Suspending session at 'Fri Jun 4 16:47:01 2010'.
> Info: Waiting the cleanup timeout to complete.
> Session: Session suspended at 'Fri Jun 4 16:47:11 2010'.
> Session: Resuming session at 'Fri Jun 4 16:48:47 2010'.
> Info: Proxy running in server mode with pid '8524'.
> Info: Waiting for connection from '127.0.0.1' on port '6000'.
> Info: Aborting the procedure due to signal '15'.
> Session: Display failure detected at 'Fri Jun 4 16:48:47 2010'.
> Session: Suspending session at 'Fri Jun 4 16:48:47 2010'.
> Session: Session suspended at 'Fri Jun 4 16:48:47 2010'.
>
>
> That's what the Nomachine NX client tells me:
> NX> 203 NXSSH running with pid: 2908
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: XXXXXXXXX on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
> NX> 105 hello NXCLIENT - Version 3.2.0
> NX> 134 Accepted protocol: 3.2.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: markus
> NX> 102 Password:
> NX> 103 Welcome to: terminalserver user: markus
> NX> 105 listsession --user="markus" --status="suspended,running"
> --geometry="1280x1024x32+render" --type="unix-kde"
> NX> 127 Sessions list of user 'markus' for reconnect:
>
> Display Type Session ID Options Depth
> Screen Status Session Name
> ------- ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
> 2000 unix-kde D7E1A5D627ED20667867EBBB74C88FCB -RD--PSA 32
> 1274x962 Suspended XXXXXXXX
>
>
> NX> 148 Server capacity: not reached for user: markus
> NX> 105 res...

I am also affected by this problem. However, going back to karmic ppa version does not solve the problem for me: With lucid ppa version the existing session on the server would just die upon new connection atempt, and a new session got created. With the karmic ppa version existing sessions stay alive, but an additional new session is always created (I am not offered the option to reconnect an existing session). Not much of a difference from the user's point of view. Could it depend on the client version (I'm using 3.4.05 or 3.4.07)? Or is it linked to some config option? I am quite confident I was using default options for freenx in karmic before I upgraded to lucid.
Haven't tried neatnx so far, but from comments I've read, it does not seem to be the panacea either.
Is there a point trying the testing ppa versions?

Same here since lucid upgrade, except I get this message in the server's log when trying to reconnect to a suspended session
:
NX> 1004 Error: Could not resume session. nxagent process could not be found.

More detailled:

Info: Using /etc/nxserver/nxacl to change session parameters or deny session.
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.0)
nxnode_reader: NX> 1009 Session status: resuming
NX> 1009 Session status: resuming
server_nxnode_echo: NX> 1009 Session status: resuming
nxnode_reader: NX> 710 Session status: running
nxnode_reader: NX> 1002 Commit
nxnode_reader: NX> 1006 Session status: running
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
server_nxnode_echo: NX> 710 Session status: running
server_nxnode_echo: NX> 1002 Commit
session_status 9DFE94702C82FB497C5E03F2CFF73FAF Running
server_nxnode_echo: NX> 1006 Session status: running
nxnode_reader: NX> 1004 Error: Could not resume session. nxagent process could not be found.
nxnode_reader: NX 1004> kill 23782
NX> 1004 Error: Could not resume session. nxagent process could not be found.
NX 1004> kill 23782
NX> 105 server_nxnode_echo: NX> 596 Session startup failed.
NX> 596 Session startup failed.

This version has a feature that it caches the session list for 30 seconds.
It works great, but if you want it to resume a just closed session it will fail.

shouldn't it fail? please excuse my observation.
Closed not the same as suspended, right?

Lewis

On Tue, Jun 15, 2010 at 5:10 PM, Marcelo Boveto Shima <
<email address hidden>> wrote:

> This version has a feature that it caches the session list for 30 seconds.
> It works great, but if you want it to resume a just closed session it will
> fail.
>
> --
> [lucid] [regression] Session resume not working anymore
> https://bugs.launchpad.net/bugs/589723
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>

Marcelo, this version is seriously broken. It doesn't work at all. The sessions don't even remember the current one let alone any.

Ok I will revert to the karmic one.

Wolfgang Lorenz just sent me a patch.
Please test version 0.7.3.git100327.e224628-0~ppa7~lucid uploaded to the ppa

version 0.7.3.git100327.e224628-0~ppa7~lucid works for me! thank you!

It still wasn't working for me, but it seemed to be a permission issue on /var/lib/nxserver/db/running which should be owned by the nx user and group, but was owned by root. Once I changed the permissions it worked just fine.

Jeremy's fix is works for me, and I agree with DodgeThis about NeatX, apart from being slow, it is not stable or ready for use by the average user, I think the Ubuntu Docs should be amended to not recommend its usage over FreeNX (once the permissions issues get fixed!!!):

https://help.ubuntu.com/community/FreeNX

This is just leading people towards disaster with NeatX, FreeNX is the way to go for now...

oh, and for those who just want to cut and past, based upon what Jeremy said:

sudo chown -R nx /var/lib/nxserver/db/running
sudo chgrp -R nx /var/lib/nxserver/db/running

fixed FreeNX for me, and I am using the "qtnx" client, which does not seem to work with NeatX (had to use nomachine.com's non-open source version)

Sorry for my late respone.
I've upgraded freenx today to the latest lucid version and now suspend/resume seems to work fine again!

Keep on your work!

Too bad, I've a new problem with 0.7.3.git100327.e224628-0~ppa7~lucid:
Session suspend/resume does not work between Windows and Linux - so if I start a session with nxclient running on Linux I can't resume the session with nxclient running on Windows and vice versa. That worked fine with the karmic version.

The nxclient that can't resume a session just presents me a session list with my only session, but the resume button is grayed out (and the "status" column is empty?)

Someone?

Sounds like it might be a flashback of the different color depth resume issue. If the color depth of Linux and windows differs NX doesn't resume. Only problem was it was so picky it wouldn't resume a 32bit color (windows) on a 24bit Linux (really 32bit, but Linux reports as 24bit). I have Windows as well, so I can test it.

I think I've been able to locate the Windows vs. Linux resume problem, but I'm not that sure, how to fix it cleanly. I've attached a patch (more a hack) that solves the problem for me, but I'm sure it's not really clean - but it should be enough to point to the real problem.

That doesn't look like the color fix to me.

This is the original diff file that fixed this problem, but there is no guarantees this is still the problem.

That was the old patch and will not apply to the current version of freenx. Here is the updated patch.

I tested with applying that patch from 3 years ago and it worked. Not sure why this version has so many regressions though. This fix should have been there since the beginning almost. Fortunately it was still in the patch history on our servers. For those that are suffering with the problem, you can edit /usr/lib/nx/nxserver directly and add the two lines yourself and session resume between Windows and Linux should work again.

I will try to roll out a new updated package with that patch included, but it might not be for two more weeks. Meanwhile I am going to try to get this patch included into the git source.

Same problem can been seen switching between OS X and Linux, and the fix Jeremy provided for /usr/lib/nx/nxserver solved it for me.

I don't think that this is a color issue (at least on my setup with hardy (ubuntu 8.04) and freenx 0.7.3+teambzr104-0freenxteam1~hardy1

as it occurs even when I put color depth to 24 bit on windows xp. Also those two lines are already in my /usr/bin/nxserver:

depth=$(getparam screeninfo | cut -d "x" -f3 | cut -d "+" -f1 )
                        [ "$depth" = "32" ] && depth=24
                        geom=$(getparam screeninfo | cut -d "x" -f1,2)
                        render=$(getparam screeninfo | cut -d "+" -f2 )
                        available="N/A"
                        udepth=$(echo $3 | cut -d "x" -f3 | cut -d "+" -f1 )
                        [ "$udepth" = "32" ] && udepth=24
                        urender=$(echo $3 | cut -d "+" -f2 )

I tried adding the hack from Marcus as well,

stringinstring "unix-" "$4" || available="N/A"
+ available="$(getparam status)"

but it also didn't resolve the issue.

nxclient still exits when I try to shadow system session from windows (works from linux just fine of course)

Hi Matt, I think that your problem is related to this bug:
https://bugs.launchpad.net/freenx-server/+bug/380694

The results are the same, nxclient exits when you try to shadow from windows. The difference is in /var/log/kern.log where you will see something similar to this:

... nxagent[18383]: segfault at 2c ip 00000000004ae7b0 sp 00007fffa0f08130 error 6 in nxagent[400000+4e0000]

I'm pretty sure that Dept. Tecnico is correct about this Matt. There is definitely a problem with this. It may be related to a library incompatibility or a failure to load the shadow libraries. What is your X Server version and system version?

Greetings,

I'm installed free-nx on ubuntu 12.04 and I am able to create sessions from both windows and OSX w/out issue. However, I am unable to resume any session from anywhere.

I'm including the entire resume portion of /var/log/nxserver.log but it doesn't appear all that helpful. I am seeing now errors in any of the other standard log files, kern.log, syslog, etc. etc.

Any assistance would be very swell.
Thanks,
--Gary

---- cut here ----
server_nxnode_echo: NX> 1005 Session status: suspended
-- NX SERVER START: - ORIG_COMMAND=
-- NX SERVER START: - ORIG_COMMAND=
Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: gpwolfe
NX> 102 Password:
Info: Auth method: ssh gpwolfe@127.0.0.1's password:
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 716 Slave mode started successfully.
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
nxnode_reader: NX> 716 finished
nxnode_reader: NX> 1001 Bye.

NX> 103 Welcome to: jupiter user: gpwolfe
NX> 105 listsession --status="suspended,running" --type="shadow"
NX> 127 Sessions list of user 'gpwolfe' for reconnect:

Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
2000 unix-gnome 93A2221D0BD91C784D9181A90F1526EB --D--PSA 24 1203x752 Suspended jupiter%28external%29 (gpwolfe) (Shadowed)
0 Local FF474599A8878CD20260F7EA15D17369 -------- Running X0 (Local)
0 Local 28FE526C36F0E70293DC258E7EB75A77 -------- Running X0 (Local)

NX> 148 Server capacity: not reached for user: gpwolfe
NX> 105 listsession --status="suspended,running" --type="shadow"
NX> 105 restoresession --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --samba="1" --cups="1" --media="1" --render="1" --session="jupiter%28external%29" --type="unix-gnome" --geometry="1203x752" --keyboard="pc105/us" --client="macosx" --id="93A2221D0BD91C784D9181A90F1526EB"

Info: Using /etc/nxserver/nxacl to change session parameters or deny session.
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
nxnode_reader: NX> 700 Session id: jupiter-2000-93A2221D0BD91C784D9181A90F1526EB
nxnode_reader: NX> 705 Session display: 2000
nxnode_reader: NX> 703 Session type: unix-gnome
server_nxnode_echo: NX> 700 Session id: jupiter-2000-93A2221D0BD91C784D9181A90F1526EB
nxnode_reader: NX> 701 Proxy cookie: 9a03e486fab788a998939899c337ed1a
nxnode_reader: NX> 702 Proxy IP: 127.0.0.1
NX> 700 Session id: jupiter-2000-93A2221D0BD...