Unable to resume a session on Vista error : Could not find ':' in DISPLAY: about neatx HOT 11 OPEN

This is pretty odd. Can you please post the full session logs from 
/var/log/user.log
when this happens? Thanks.

[deleted comment]

Sorry for the delay, here's the log file.

There seem to be two seperate problems. One is the "':' in DISPLAY" error, and 
the
other is the failure to resume the session.

For the former, can you tell me what happens if you run this as the nx user?

  /bin/su XXXX -c 'cd && /usr/local/lib/neatx/nxserver --proto=3030000 -- XXXX'

I suspect it's su (or some part of pam/login process) that's causing the 
$DISPLAY
error. Neatx never reads that variable.

As for the latter, i'm puzzled as to why there were no further messages from the
session after this:

Aug 24 17:14:12 myvps1 nxnode[16712]: DEBUG nxnode:154 Resuming session

Can you tell me if the nxnode simply exits at that point? I'd have expected log
entries from it about writing session options, and sending SIGHUP to nxagent.

Here's the output : 

NX> 103 Welcome to: somehost.someserver.somewhere user: XXXX
NX> 105

Nothing happens next.

Exactly the same error using Nomachine NX Client 3.3.0-6 from Vista.

However, my user.log comes with a stacktrace.

Can you both tell me what server distro/release you're using, please? I don't 
have
access to a vista box myself, i've tested with windows 7 with no luck.

@techtonik:
That error looks like issues #21 / #23.

Also, it would be useful to know if the "Could not find ':' in DISPLAY: " error
happens when you use a non-vista client OS.

Ubuntu 9.10 (karmic) with neatx server from https://edge.launchpad.net/~freenx-
team/+archive/ppa under version 0.3.1-0ubuntu4~karmic1

Unfortunately, I do not have any other non-vista desktop box at my disposal at 
this 
time.

@kormat: I can't get to the step with session names in my client.

Seems like there is indeed issue with inability to resume session after reset 
on server 
side like described in issue #21

When I cleaned up /var/lib/neatx/sessions I could connect again under the same 
session 
name. Otherwise I have to rename session to something else (the similar 
workaround as 
in issue #19)

Just ran into the same issue with 0.3.1.  Thanks for pointing to the workaround.