Fritz Elfert - 2009-07-30

Nope, wrong assumption ...
This is how it is supposed to work (NoMachine's client does this as well). NX always uses two stages of authentication:

  1. Login into the nxserver, always using a key (default: NoMachine's well known pubkey, but can be pasted in the advanced config). Also: this is always done as user nx, not the user you specify in the login dialog.
  2. The actual user/password based login versus nxserver's command-shell inside the first connection.

What you see (the execvp message) is from stage 1. Error 2 is ENOENT and this means: Your nxssh binary (/home/tgc/opennx/src/opennx/bin/nxssh) could not be found. Apparently, you are trying to run an uninstalled opennx from within the source directory. This cannot work without changes. Reason: Just like NoMachine's original, when started for the first time, OpenNX finds out it's own path and sets a config variable "System NX dir" to the parent directory. This makes perfect sense if installed in /usr/NX/bin but fails in your case.

Two solutions are possible:
1. remove OpenNX's environment-config file at ~/.opennx, install opennx into /usr/NX/bin, then try again.
2. If you just want to try it out without installing, Start OpenNX, select "Configure", select the "Environment" tab. Correct the "System NX dir" (should point to /usr/NX, or whereever your regular nx env is) entry, klick apply.

Please use the mailing list for further help and/or discussion.