[FreeNX-kNX] FreeNX & NoMachine Player - Connection Issues

Sat Jan 19 16:56:35 UTC 2013

freenx-knx-bounces at kde.org wrote on 19/01/2013 16:15:21:

[SNIP]
> First, we've tried OpenNX and not been overly successful getting it 
> running.  Second, because NX Player seems to work fine with FreeNX 
> on CentOS, NX Server 3.5, and the NoMachine 4 Preview, I think the 
> client is not the issue and that NX Player should work fine.  I 
> suspect the issue is in the FreeNX + OpenSuSE combo.

Yup.

Try OpenNX just to see if it works OK then.

There are a few issues with Suse

e.g.
There is a library version issues with OpenSuse 12.2 which trips up
nxagent with
        undefined symbol: _XGetRequest

if you don't include the old libcomposite in the NX-3.4. . . . .rpm

> 
> > 
> > 
> > Note FYI
> > 
> > There is an open "X" font rendering bug between
> >          OpenSuse 12.2 and the Nomachine Windows client
> > which
> >          the OpenNX cliient doesn't have . . . 
> > 
> > so Nomachine aren't worrying too much about Suse
> 
> Hmmm...we haven't run into this one, yet.

I don't use 12.1 so you might not get it there . . .

[SNIP]
> > Do you have FreeNX AND Nomachine V4 on the same Suse machine ??
> > 
> > Do you have connections to both at the same time ???
> > 
> > Is thete any overlap of resorces . . .
> 
> No x 3.  I have identical SuSE systems (openSuSE 12.1) that I'm 
> trying to connect to.  Once has NoMachine 4 Preview, the other has 
> FreeNX.  NX Player connects to the Preview fine, but not to FreeNX 
> on openSuSE.

Good. I was wondering . . . but read on a little about 2 servers

[SNIP]

> >> server_nxnode_echo: NX> 1001 Bye.
> >> Info: Closing connection to slave with pid 27540.
> >> 
> >> - Finally, if I look at the user-specific logs mentioned, I see:
> >> Error: The remote NX proxy closed the connection.
> >> Error: Failure negotiating the session in stage '10'.
> >> Error: Aborting session with 'Unable to open display 'nx/nx,
> >> options=/home/nxtest/.nx/C-
> >> se003945-11000-7CE6ABAB93B40AE2CB8303E679FBE39C/options:11000''.
> >> Session: Aborting session at 'Fri Jan 18 19:57:45 2013'.
> >> Session: Session aborted at 'Fri Jan 18 19:57:45 2013'.
> >> xrdb: Connection refused
> >> xrdb: Can't open display ':11000'
> >> /usr/bin/startxfce4: X server already running on display :11000
> > 
> > already running . . . XAuth issue probably
> > 
> > 
> > Update the FreeNX server
> > 
> >                 #DISPLAY_BASE=1000  ( or whatever. if it's # ed out, 
the 
> > value is set by nxloadconfig )
> >                 DISPLAY_BASE=(your value)
> > 
> > parameterin /etc/nxserver/node.conf
> > 
> > and try a value other than 11000 or 1000
> 
> Okay, I will try that, but I think I've tried a few other values 
> there and nothing seems to make a difference.  I'll try something in
> the 2000-5000 range or something like that to see if that helps.

The issue to which I refer is caused by connecting to two
NX servers simultaneously, if the nxclient X (server) tries to map
both NX servers to the same nxclient display.

So
the DISPLAY_BASE value needs to be unique for each FreeNX server
to which you may be simultaneously connecting.

Are you connecting to more than one ???

> 
> > 
> > 
> >> xrdb: Connection refused
> >> xrdb: Can't open display ':11000'
> >> xscreensaver: 19:57:45: Can't open display: :11000
> >> xscreensaver: 19:57:45: running as nxtest/users (120/100)
> >> 
> >> xscreensaver: 19:57:45: Errors at startup are usually authorization 
> > problems.
> >>               But you're not logging in as root (good!) so something
> >>               else must be wrong.  Did you read the manual and the 
FAQ?
> >> 
> >>               http://www.jwz.org/xscreensaver/faq.html
> >>               http://www.jwz.org/xscreensaver/man.html
> >> 
> >> 
> >> ** ERROR **: Cannot open display: 
> >> /etc/xdg/xfce4/xinitrc: line 159: 28167 Trace/breakpoint trap 
> > xfce4-session
> >> 
> >> 
> >> So, can anyone shed any light on what's going on here??  First, it 
> >> seems like the server and client are both pointing the finger at 
> >> each other saying it's the other's fault.  But then there's this 
> >> error about Unable to open display??  I should also note that I have
> >> tried and successfully been able to do the "ssh -X <hostname> 
> >> nxagent" test - works fine, once it's running I can open up items 
> >> inside that display, etc.  Also, on NXPlayer, if I do a custom 
> >> session and specify xterm as the command to run, that seems to work 
> >> every time.  So, perhaps it's a timing thing - the window manager 
> > 
> > It might be timing i.e nxagent hasn't had time to start
> >          rather than it can't because :11000 is in use
> 
> :11000 isn't in use by anything else on the system - I did check that.

What about on the nxclient ????

> 
> > 
> > Test . . .
> > If you try a number of connections one after the other
> >         does it fail to connect a few times
> >         then connect eventually
> >         and keep connecting if you disconnect/re-cconect
> >         a few times ??
> 
> 
> Yes, if I continue to try it over and over, I'll eventually get a 
> good session.  It doesn't seem to matter how rapidly I 
> disconnect/reconnect, it just works 1/10 times or something like 
> that (random, I'm sure - it isn't *exactly* 1/10 times, just roughly
> in that area).  I didn't try the disconnect/reconnect 
> (suspend/resume), yet, but I'll give that a shot - I was just trying
> to get the basic connection working before I got to the other 
> complications :-).
> 
> > 
> > 
> >> trying to start before X is available, or maybe X is timing out too 
> >> fast before the window manager can start?  Also, what happens in 
> >> "Stage '10'"?  This is a fairly consistent error - failure 
> >> negotiating the session in stage '10' - but I cannot find any 
> >> reference to this error around, nor can I figure out what stage 10 
> >> is supposed to be.
> >> 
> >> Thanks, in advance,
> >> Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130119/925fc9aa/attachment.html>