<br><tt><font size=2>freenx-knx-bounces@kde.org wrote on 19/01/2013 16:23:38:<br>
<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>
</font></tt>
<br><tt><font size=2>Maybe, but agent also runs when you run xterm which
you say works every time . . </font></tt>
<br>
<br>
<br><tt><font size=2>> > <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>
> <br>
> So, changing the display base to 2500 did not help. Don't think
<br>
> that's the issue.<br>
</font></tt>
<br>
<br><tt><font size=2>The issue you have is that nxagent won't start (on
:11000)</font></tt>
<br><tt><font size=2>or</font></tt>
<br><tt><font size=2>if it does it won't keep running 'cos it can't open
the display :11000</font></tt>
<br>
<br><tt><font size=2>> Error: Aborting session with 'Unable to open
display 'nx/nx,options=/home/nxtest/.nx/C-se003945-11000-7CE6ABAB93B40AE2CB8303E679FBE39C/options:11000''.</font></tt>
<br>
<br><tt><font size=2>**** OR ****</font></tt>
<br>
<br><tt><font size=2>nxagent is running on :11000</font></tt>
<br><tt><font size=2>and</font></tt>
<br><tt><font size=2>your </font></tt>
<br><tt><font size=2> startxfe4</font></tt>
<br>
<br><tt><font size=2> is trying to start YET ANOTHER X on :11000</font></tt>
<br>
<br><tt><font size=2>> xrdb: Can't open display ':11000'<br>
> /usr/bin/startxfce4: X server already running on display :11000<br>
> xrdb: Connection refused</font></tt>
<br>
<br><tt><font size=2>which would explain why xterm works.</font></tt>
<br>
<br><tt><font size=2>*** Try running an xterm and run startkde within the
xterm ***</font></tt>
<br>
<br>
<br>
<br>
<br><tt><font size=2>> Error: Failure negotiating the session in stage
'10'.</font></tt>
<br>
<br><tt><font size=2>try</font></tt>
<br><tt><font size=2> grep -i
stage /usr/bin/nx*</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>What is in the server log just before all this . .
.</font></tt>
<br><tt><font size=2><br>
> - If I look at the logs on the server (with logging turned up a bit),
I see:<br>
> bye<br>
> Bye<br>
> NX> 999 Bye<br>
> Info: Closing connection to slave with pid 27540.<br>
> nxnode_reader: 1001 Bye</font></tt>
<br>
<br>
<br><tt><font size=2>Clean up any/all the nx processes on your server and
start again</font></tt>
<br><tt><font size=2>with a new connection.</font></tt>
<br>
<br><tt><font size=2>If the session falls over, look to see what is still
running.</font></tt>
<br><tt><font size=2>Is something holding on to display :11000</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>> <br>
> I did try the disconnect/reconnect, and I get very similar behavior
<br>
> - fails with the Error is 22 on the client most of the time, but <br>
> succeeds periodically. Haven't dug into the logs, yet, but I'll
take a look.<br>
> <br>
> -Nick<br>
</font></tt>