QtNX and nxproxy
Posted by George Wright Sun, 27 Aug 2006 17:31:00 GMT
I have had several emails in the last few days about QtNX which all detail a common problem.
QtNX, as you should know, requires nxssh and nxproxy to function properly. These need to be in the PATH and their relevant libraries in LD_LIBRARY_PATH. Without that, QtNX will not function.
On top of that, QtNX requires nxproxy 1.5.0. Version 2.0.0 does not work, so please don’t use that unless you want to try and port QtNX to nxproxy 2.0.0. I will look into porting it to 2.0.0 but I do not see it as urgent right now.
However, even though nxproxy 1.5.0 is used, I am reliably informed that it will connect to an NX 2.0.0 server without any trouble whatsoever - so there’s no need to worry about that.

Nomachine doesn’t seam to offer 1.5 for download anymore. They also offer a free GPL nxserver with version 2.0, so I think it’s important to make QtNX work for NX 2.0 as well.
NoMachine does offer 1.5.0 for download. If you go to http://www.nomachine.com/sources.php then click on 1.5.0 you can download the 1.5.0 sources.
George, I’ve tried to build the libraries from NoMachine, and I’ve completely failed. :)
I started building nxproxy and nxssh (because are the ones you mention), and they fail with a “missing -lXcomp”.
So I’ve tried to compile nxcomp, but it also fails with “ISO C++ forbids declaration of ‘RenderMinorExtensionStore’ with no type”.
BTW, in nomachine’s website there is 1.5. Just click the optioin.
You need a patch for nxcomp to compile using gcc 4. Search the freenx-knx mailing list for it.
Hi George,
I got nxclientlib and qtnx compiled, but on running it is not able to start the session. Authentication happens properly, but for some reason the session fails to start. The nomachine client, with the same settings (including key) as that given to qtnx, opens up a gnome desktop just fine.
I will send you a mail with the relevant logs (both from the nomachine as well as the log window in qtnx).
nxproxy, nxssh etc are all in path, and their relevant libraries are, too. And it’s all 1.5
Does it connect against the 2X NX server? It is version 1.5.0
Looks like this really has potential, especially as Knx seems to have stalled. I’d really love to see this proted to 2.0.x/2.1.x, as I’m a Fedora user and that’s the version in Extras. If this were to happen, I’d be happy to package it for Extras, if no one has plans to already. The CHANGELOG for the current nx Extras package indicates intended support for qtnx.
+1 on updating it to support 2.1…
I was able to build an RPM of it for FC5, but I couldn’t get it working. I used atrpms nx-1.5 and freenx-0.4.4, but they lack nxssh, so is a no-go.
I also tried for kicks the nx-2.1 and freenx-0.5.0 from FC5-extras. But nxagent fails, as you point out it would. It looks promising though.
NX, for me, has always been “almost”. With qtnx sync’d up to the latest NX release I think we’d finally be there.
Thanks for your work,
-Jeff
very good
I just read through the entire article of yours and it was quite good. This is a great article thanks for sharing this information. I will visit your blog regularly for some latest post.
I might get the code out, muck around with it a bit, and send you a patch or two
Crease ralph lauren polo to go buying them. steer obvious of using cable Vetement ralph Lauren means fashion.