Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8510 - nxclient package issues
Attached to Project:
Arch Linux
Opened by Darwin Bautista (djclue917) - Monday, 05 November 2007, 04:59 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 12 January 2008, 13:14 GMT
Opened by Darwin Bautista (djclue917) - Monday, 05 November 2007, 04:59 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 12 January 2008, 13:14 GMT
|
DetailsDescription:
missing file: /opt/NX/share/keys/server.id_dsa.key - the NX Connection Wizard complains about this upon its startup (error: Cant't read default ssh key "/opt/NX/share/keys/server.id_dsa.key"!) - without the file, the client won't be able to connect to an NX server (error: DSA key is corrupted or has been protected with a passphrase) /opt/NX/bin/nxclient-nomachine should be renamed to /opt/NX/bin/nxclient (or symlinked) because all the shortcuts created by the NX Connection Wizard points to /opt/NX/bin/nxclient (error: KDEInit could not launch '/opt/NX/bin/nxclient'.) Minor stuff (just a thought): why use the RPMs (which would need rpmextract as a makedepend) when tarballs are available? Additional info: * nx-common 3.0.0-3 * nxclient 3.0.0.84-1 Steps to reproduce: 1. Create a connection via NX Connection Wizard 2. Use the shortcut to connect. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Saturday, 12 January 2008, 13:14 GMT
Reason for closing: Implemented
Saturday, 12 January 2008, 13:14 GMT
Reason for closing: Implemented
- this is normal and mentioned in freenx wiki. -> not an issue, that's how nx works
/opt/NX/bin/nxclient-nomachine should be renamed to /opt/NX/bin/nxclient (or symlinked) because all the shortcuts created by the NX Connection Wizard points to /opt/NX/bin/nxclient (error: KDEInit could not launch '/opt/NX/bin/nxclient'.)
- i'll change that this wasn'T possible with nx <=0.7.1
rpm is used because it's more complete than tarball, at least it ever worked as it should, tarball was not always working
Please copy '/opt/NX/home/nx/.ssh/client.id_dsa.key' to ..."? If so, then this no longer works. The path no longer exists. (Sorry I have to use the re-open request.)
"/opt/NX/home/nx/.ssh/client.id_dsa.key this file contains the correct key for the client." -> this doesn't exist when only nxclient is installed. The server I'm trying to connect to uses the default key.
(1) Custom keys for each session can be imported or manually added using nxclient (without having to copy anything to /opt/NX/share/keys/). (2) Also, there is a "Default" button which can automatically import the default key (/opt/NX/share/keys/server.id_dsa.key). Lastly, I think having the default key in the nxclient package is more convenient because of (1) and (2).