[ opennx-Bugs-2844795 ] NX Session doesn't startup: cannot open display

[SourceForge.net <no...@so...>]

Bugs item #2844795, was opened at 2009-08-26 10:30
Message generated for change (Settings changed) made by felfert
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: Rejected
Priority: 5
Private: No
Submitted By: Sebastian Reitenbach (buzzzzdeeee)
Assigned to: Fritz Elfert (felfert)
Summary: NX Session doesn't startup: cannot open display

Initial Comment:
Hi,
I tried a long time to get a NX session working. So I tested the obvious things:
The server is an openSUSE 11.1, the client is OpenBSD 4.5/opennx-0.16

ssh -X nxserver; nxnode --agent
that worked I got the Black screen with the !M
also nxssh -nxadminmode -X user@nxserver konsole
was working, I got the remote KDE konsole on my OpenBSD desktop.

So I took a look into the code and found in MySession.cpp in line 1663
I changed the line from:
nxsshcmd << wxT(" -nx -x -2")
to
nxsshcmd << wxT(" -nx -X -2")

and recompiled. Afterwards the nxsession started to work.

Sebastian

----------------------------------------------------------------------

>Comment By: Fritz Elfert (felfert)
Date: 2009-09-19 01:08

Message:
No further response from submitter. Therefore: closed

----------------------------------------------------------------------

Comment By: Fritz Elfert (felfert)
Date: 2009-08-29 00:54

Message:
Apparently, your NX Server is completely misconfigured.
If you are using -X instead of -x, then you are using regular ssh
X11-forwarding, *not* the NX protocol (It works accidently - because nxssh
is derived from openssh and that old code is still in there). To use
*that*, you wouldn't need NX (or OpenNX) at all.

Therefore:
The -x (disable X11-Forward) parameter is absolutely correct and
intentional.

The *normal* way (with X111-Forwarding disabled by -x) is, that the
DISPLAY variable is dynamically set up on the server side. What software
are you using at the server side? NoMachine's original, FreeNX or neatnx?
Also: NX *always* uses a 2-stage login process where the first user is
always the "nx" user, then, session parameters are negotiated, and after a
second local authentication on the server side, the server-side agent is
started, (which - depending on session parameters - in turn starts either a
local X-Session or uses rdesktop or xvnc for connecting to some remote
machine).

Have you tried to connect using the original (NoMachine's) client? I bet,
this would not work either with your server setup. Also: To get a clue
about what is going wrong, Try connecting with OpenNX (unchanged, with -x)
and have a look at ~/.nx/temp/<PID>/{runlog,sshlog}

Cheers
 -Fritz

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662