<br><tt><font size=2>freenx-knx-bounces@kde.org wrote on 19/01/2013 16:15:21:<br>
<br>
[SNIP]</font></tt>
<br><tt><font size=2>> First, we've tried OpenNX and not been overly
successful getting it <br>
> running. Second, because NX Player seems to work fine with FreeNX
<br>
> on CentOS, NX Server 3.5, and the NoMachine 4 Preview, I think the
<br>
> client is not the issue and that NX Player should work fine. I
<br>
> suspect the issue is in the FreeNX + OpenSuSE combo.</font></tt>
<br>
<br><tt><font size=2>Yup.</font></tt>
<br>
<br><tt><font size=2>Try OpenNX just to see if it works OK then.</font></tt>
<br>
<br><tt><font size=2>There are a few issues with Suse</font></tt>
<br>
<br><tt><font size=2>e.g.</font></tt>
<br><tt><font size=2>There is a library version issues with OpenSuse 12.2
which trips up</font></tt>
<br><tt><font size=2>nxagent with</font></tt>
<br><tt><font size=2> undefined symbol:
_XGetRequest</font></tt>
<br>
<br><tt><font size=2>if you don't include the old libcomposite in the NX-3.4.
. . . .rpm</font></tt>
<br>
<br>
<br><tt><font size=2>> <br>
> > <br>
> > <br>
> > Note FYI<br>
> > <br>
> > There is an open "X" font rendering bug between<br>
> > OpenSuse 12.2 and the Nomachine
Windows client<br>
> > which<br>
> > the OpenNX cliient doesn't
have . . . <br>
> > <br>
> > so Nomachine aren't worrying too much about Suse<br>
> <br>
> Hmmm...we haven't run into this one, yet.<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>I don't use 12.1 so you might not get it there . .
.</font></tt>
<br>
<br>
<br><tt><font size=2>[SNIP]</font></tt>
<br><tt><font size=2>> > Do you have FreeNX AND Nomachine V4 on the
same Suse machine ??<br>
> > <br>
> > Do you have connections to both at the same time ???<br>
> > <br>
> > Is thete any overlap of resorces . . .<br>
> <br>
> No x 3. I have identical SuSE systems (openSuSE 12.1) that I'm
<br>
> trying to connect to. Once has NoMachine 4 Preview, the other
has <br>
> FreeNX. NX Player connects to the Preview fine, but not to FreeNX
<br>
> on openSuSE.<br>
</font></tt>
<br><tt><font size=2>Good. I was wondering . . . but read on a little about
2 servers</font></tt>
<br>
<br>
<br><tt><font size=2>[SNIP]</font></tt>
<br><tt><font size=2><br>
> >> server_nxnode_echo: NX> 1001 Bye.<br>
> >> Info: Closing connection to slave with pid 27540.<br>
> >> <br>
> >> - Finally, if I look at the user-specific logs mentioned,
I see:<br>
> >> Error: The remote NX proxy closed the connection.<br>
> >> Error: Failure negotiating the session in stage '10'.<br>
> >> Error: Aborting session with 'Unable to open display 'nx/nx,<br>
> >> options=/home/nxtest/.nx/C-<br>
> >> se003945-11000-7CE6ABAB93B40AE2CB8303E679FBE39C/options:11000''.<br>
> >> Session: Aborting session at 'Fri Jan 18 19:57:45 2013'.<br>
> >> Session: Session aborted at 'Fri Jan 18 19:57:45 2013'.<br>
> >> xrdb: Connection refused<br>
> >> xrdb: Can't open display ':11000'<br>
> >> /usr/bin/startxfce4: X server already running on display
:11000<br>
> > <br>
> > already running . . . XAuth issue probably<br>
> > <br>
> > <br>
> > Update the FreeNX server<br>
> > <br>
> > #DISPLAY_BASE=1000
( or whatever. if it's # ed out, the <br>
> > value is set by nxloadconfig )<br>
> > DISPLAY_BASE=(your
value)<br>
> > <br>
> > parameterin /etc/nxserver/node.conf<br>
> > <br>
> > and try a value other than 11000 or 1000<br>
> <br>
> Okay, I will try that, but I think I've tried a few other values <br>
> there and nothing seems to make a difference. I'll try something
in<br>
> the 2000-5000 range or something like that to see if that helps.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>The issue to which I refer is caused by connecting
to two</font></tt>
<br><tt><font size=2>NX servers simultaneously, if the nxclient X (server)
tries to map</font></tt>
<br><tt><font size=2>both NX servers to the same nxclient display.</font></tt>
<br>
<br><tt><font size=2>So</font></tt>
<br><tt><font size=2>the DISPLAY_BASE value needs to be unique for each
FreeNX server</font></tt>
<br><tt><font size=2>to which you may be simultaneously connecting.</font></tt>
<br>
<br><tt><font size=2>Are you connecting to more than one ???</font></tt>
<br>
<br><tt><font size=2><br>
> <br>
> > <br>
> > <br>
> >> xrdb: Connection refused<br>
> >> xrdb: Can't open display ':11000'<br>
> >> xscreensaver: 19:57:45: Can't open display: :11000<br>
> >> xscreensaver: 19:57:45: running as nxtest/users (120/100)<br>
> >> <br>
> >> xscreensaver: 19:57:45: Errors at startup are usually authorization
<br>
> > problems.<br>
> >> But you're
not logging in as root (good!) so something<br>
> >> else must
be wrong. Did you read the manual and the FAQ?<br>
> >> <br>
> >> </font></tt><a href=http://www.jwz.org/xscreensaver/faq.html><tt><font size=2>http://www.jwz.org/xscreensaver/faq.html</font></tt></a><tt><font size=2><br>
> >> </font></tt><a href=http://www.jwz.org/xscreensaver/man.html><tt><font size=2>http://www.jwz.org/xscreensaver/man.html</font></tt></a><tt><font size=2><br>
> >> <br>
> >> <br>
> >> ** ERROR **: Cannot open display: <br>
> >> /etc/xdg/xfce4/xinitrc: line 159: 28167 Trace/breakpoint
trap <br>
> > xfce4-session<br>
> >> <br>
> >> <br>
> >> So, can anyone shed any light on what's going on here?? First,
it <br>
> >> seems like the server and client are both pointing the finger
at <br>
> >> each other saying it's the other's fault. But then
there's this <br>
> >> error about Unable to open display?? I should also
note that I have<br>
> >> tried and successfully been able to do the "ssh -X <hostname>
<br>
> >> nxagent" test - works fine, once it's running I can
open up items <br>
> >> inside that display, etc. Also, on NXPlayer, if I do
a custom <br>
> >> session and specify xterm as the command to run, that seems
to work <br>
> >> every time. So, perhaps it's a timing thing - the window
manager <br>
> > <br>
> > It might be timing i.e nxagent hasn't had time to start<br>
> > rather than it can't because
:11000 is in use<br>
> <br>
> :11000 isn't in use by anything else on the system - I did check that.<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>What about on the nxclient ????</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>> <br>
> > <br>
> > Test . . .<br>
> > If you try a number of connections one after the other<br>
> > does it fail to connect a few times<br>
> > then connect eventually<br>
> > and keep connecting if you disconnect/re-cconect<br>
> > a few times ??<br>
> <br>
> <br>
> Yes, if I continue to try it over and over, I'll eventually get a
<br>
> good session. It doesn't seem to matter how rapidly I <br>
> disconnect/reconnect, it just works 1/10 times or something like <br>
> that (random, I'm sure - it isn't *exactly* 1/10 times, just roughly<br>
> in that area). I didn't try the disconnect/reconnect <br>
> (suspend/resume), yet, but I'll give that a shot - I was just trying<br>
> to get the basic connection working before I got to the other <br>
> complications :-).<br>
> <br>
> > <br>
> > <br>
> >> trying to start before X is available, or maybe X is timing
out too <br>
> >> fast before the window manager can start? Also, what
happens in <br>
> >> "Stage '10'"? This is a fairly consistent
error - failure <br>
> >> negotiating the session in stage '10' - but I cannot find
any <br>
> >> reference to this error around, nor can I figure out what
stage 10 <br>
> >> is supposed to be.<br>
> >> <br>
> >> Thanks, in advance,<br>
> >> Nick<br>
</font></tt>