Bug 405512

Summary:	Free NX Client unable to connect
Product:	[openSUSE] openSUSE 11.0	Reporter:	Josh Albright <Josh.Albright>
Component:	KDE4 Applications	Assignee:	Dirk Mueller <dmueller>
Status:	RESOLVED NORESPONSE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P2 - High	CC:	arun, drankinatty
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Josh Albright 2008-07-01 20:25:07 UTC

On two separate openSuSE 11.0 installations, the freenx client doesn't work (installing package freenx-client 0.9).  I configured the freenx server portion on openSuSE 11.0, and have successfully connected from windows and linux using No Machine's free version.

When I attempt to connect, I get prompted (in the terminal window, NOT a GUI window - another bug, but a smaller one).  After I accept the key I get the following in the terminal window:

jalbrigh@PC0011223344:~> qtnx
Process started
stderr> Warning: Identity file id.key not accessible: No such file or directory.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Password:

To verify that qtnx is capable of connecting, I used an Ubuntu 8.04 box and installed the 0.9 version of qtnx, and it worked fine.  Using the Ubuntu box as a guide, I found that the location of the id.key file should be /usr/share/qtnx - but even after copying this from the server (/var/lib/nxserver/home/.ssh/client.id_dsa.key) it still didn't work.  I'm using the "default" NX key.

Note also, that I tried the version that is in the openSuSE OSS repository, as well as the KDE4 buildservice, but neither worked.  I also tried the "qtnx" package, but that one doesn't work at all - it states "Process Failed" in the terminal window and never even asks for the key the first time.

Comment 1 David Rankin 2009-06-02 15:17:13 UTC

Stephen, Dirk;

    Has no one fixed this yet?? I get the exact same results. It looks like this bug has been open for nearly a year without any work on it. Did this package get fixed under another name that works now? Please let us know. Thanks.

Comment 2 Josh Albright 2009-06-02 16:44:02 UTC

Just as an update, I have a fresh install on completely different hardware, and I can verify the exact same behavior is exhibited on OpenSuSE 11.1 as it was on OpenSuSE 11.0.

To reiterate, I'm use the FreeNX server (although now it's on an Ubuntu server instead of a SuSE server) NOT the "offical" NX client.  I installed the freenx-client application and launched qtnx.  Same errors reported as above.  I have not attempted testing this with the "official" NX server but I'd imagine anyone who uses that would use the "official" client.

I'm surprised it's been a year and there have been no comments.  I just switched and use the "official" NX client myself now to workaround this bug.  Still using the FreeNX server though.

Comment 3 Dirk Mueller 2009-06-03 11:38:55 UTC

the reason why it works with the ubuntu client is that they patched it for the ubuntu server: 

--- qtnx-0.9.orig/qtnxwindow.cpp        2008-03-14 12:25:00.638618439 +0000
+++ qtnx-0.9/qtnxwindow.cpp     2008-03-14 12:25:34.639487284 +0000
@@ -290,7 +290,7 @@

     m_NXClient->setDepth(getDepth());

-    QString keyPath = "id.key";
+    QString keyPath = "/usr/share/qtnx/id.key";

 #ifdef Q_WS_MAC

by default it searches for id.key in your home directory.

Comment 4 Josh Albright 2009-06-03 20:26:00 UTC

That's cool, thanks for the info, I copied the appropriate id.key file from the server, and that error disappeared, however qtnx still doesn't work.  Now I get:

jalbright@joshdesktop:~> qtnx
Process started
stderr> Pseudo-terminal will not be allocated because stdin is not a terminal.

And then it will sit there, never making the connection (I checked netstat and didn't see a connection attempt to my server).  On Ubuntu, it will then make the ssh connection and I can see the dialog take place to authenticate to the NX daemon (starting with the "HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)).

Incidentally, the configure GUI in qtnx has a checkbox to say "use default key" - which doesn't make sense that you then have to copy the id file to your home directory (since the default key should really be consistent system wide).  If you had custom keys then there's a dialog box in the GUI, which then writes the custom key in your ~/.qtnx/<session>.nxml file.

I tried using xterm as well (thinking that maybe using konsole to launch caused the issue) - and no luck, xterm on Ubuntu still works fine.  The term type as specified by $TERM in konsole, gnome-terminal and xterm is 'xterm'.  Maybe there's another "ubuntu" patch which makes it work?  If so, is there a way to have it added upstream so all the distributions could benefit?

Comment 5 Arun Persaud 2009-10-14 23:12:26 UTC

Had the same problem as described in the first report. After copying /var/lib/nxserver/home/.ssh/client.id_dsa.key from the server to .qtnx/id.key on the client I was able to connect though.

Using 11.1 and the packages from the X11:Remote Desktop repository.

freenx-client 0.9 release 64.2
and on the server
FreeNX 0.7.2  release 26.1

Comment 6 Larry Finger 2011-04-04 02:34:54 UTC

The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!