Just as a note to anyone who really cares; I spent a cpl of hours yesterday in ‘build’ mode. Using the latest NX libraries downloaded from their site and the FreeNX source (0.7.2) on a Debian Lenny box… I now have a lovely working FreeNX install.

Agreed, it’s a little painful if you aren’t accustomed to the process of finding out what your ‘-dev’ dependencies are especially if they aren’t listed for you BUT… hang in there.

The only features that appear to be broken still are the VNC and session shadowing. Which is fine for me as I don’t need either as of yet.

The client I’m using everywhere (XP and Vista and Debian desktops) is the NX client from the NoMachine website.

If anyone would like a run through of my build adventure, I’d be happy to oblige.

BTW has anyone tested the crossover wine install on NX yet?
That’s my next journey.

Until then.
chins up all!
D/.

How did you go about doing that? Because I’m having the same problems Jamie is having when I try to use NX Client to connect to my Ubuntu Linux box.

I did read at the FreeNX website that I have to change the display to localhost on nxnode like this: DISPLAY=localhost:$display
the problem is I don’t know where nxnode is on my machine.

http://www.nomachine.com/ar/view.php?ar_id=AR07D00407
http://www.nomachine.com/ar/view.php?ar_id=AR05E00459

Sorry I cannot help you out: I really do not have a specific advise… For what it is worth, you might try stripping down your desktop and remove, say, the deskbar applet or the Tomboy deskbar as they seem to be incompatible with NX and could be crashing it but beyond that, I have no idea what to do. Sorry again…

I’ve just encountered the same problem and still can’t find a solution. My system setup is:

Ubuntu 7.04 AMD64nxclient 2.1.0-17 NX Client
2.1.0-22 NX Server Node
2.1.0-22 NX Server

(all the NX deb packages were i386). I’ve installed the same deb packages on another Ubuntu 7.04-i386 machine and they worked perfectly.

The symptom I had was the same as discussed above: after authentication I get nothing but black screen, with the top-left corner being grey/yellowish. Pressing ENTER/ESC does not help at all. I’ve tried to login in via various users on the system, including users that have never being logged in via keyboard, but always ended up with the same problem.

any idea how this problem can be addressed?

tia,

I beleive it is the box which says ‘Locally I am expecting one type of keyboard, but the keyboard using me is something different. Yes/No’ Sorta thing.

Just thrash the keys. At least thats what I did. It only happend once.

One thing I’m trying to get straightened out, however, is I cannot successfully log “straight” into Gnome. I can connect into Gnome, but I get a mostly black screen with a small area to the upper-left (see Jamie’s comment above). If I move the mouse to that area, the cursor changes from an “X” to a text cursor. No other decorations or anything else on the screen. If I tell it to log into XDM, I get the login screen, where I have to log into my desktop. I’d like the NX session to handle all of that – just log me right into my Gnome desktop (I’ve already authenticated – right?).

Anyway – just blathering on. I have Feisty on one older laptop that my wife uses, plus two more desktop machines. It still has a ways to go, but every release is cooler and cooler. Feisty is the first release where almost every WiFi device can be make workable in a relatively short amount of time. Previous to this, it was a pain and a half.