January 6, 2014 at 17:38 #1553
When I connect with NX, I get the Ubuntu login screen and can type in my password. However, once I type my password and hit enter, the connection either drops or I am shown a version of my desktop which is frozen and I can’t interact with.
I’m using the free version of NX4 with a Windows 7 client and Ubuntu 13.04 server. I’ve attached debug logs.
Attachments:January 7, 2014 at 12:52 #1557drichardParticipant
What I have found is the best way to debug these situations with NX is to see what’s happening behind the scenes. First thing you do is find what script is being run upon login from the .cfg files, usually this is something like /etc/gdm/Xsession or /etc/xdm/Xsession or similar. Then I add a line at the top like:
env | sort > /tmp/nxenv.log
This gives you information about the variables that have been set. Then on the next line you can do a /usr/bin/xterm, which bring up a console window. If this opens and works, then NX is having trouble interacting with the desktop in some way. You can then manually start the desktop environment by hand and watch the command spewage to see what happens. Good luck!January 7, 2014 at 12:56 #1576
Hi chengas123, looks like this problem here: https://www.nomachine.com/TR12K04107.
You can sign up to receive notification when the fix has been officially released.January 20, 2014 at 09:58 #1758
I upgraded to Ubuntu 13.10 and am still having the problem. What I have figure out though is that I go to the machine and physically log on then I can connect with NX. However, if I reboot and try to first logon with NX then I cannot connect.January 20, 2014 at 09:59 #1757
@drichard, thanks for the tip. I see in /usr/NX/etc/node.cfg a reference to /etc/X11/Xsession default. However, adding “env | sort > /tmp/nxenv.log” to the top of /etc/X11/Xsession does not output anything to /tmp/nxenv.log. Am I looking at the right setting in the right file?
# Specify path and name of the command to start a new virtual desktop,
# by default the X session set on the system.
DefaultDesktopCommand “/etc/X11/Xsession default”
@Britgirl, thanks for the reference to the bug. This happens to me everytime I try to connect and makes the product unusable, so maybe it could be prioritized higher than “minor”?
Thanks to you both!!January 22, 2014 at 18:36 #1816
It won’t make the scheduled 4.1, but developers definitely have it at the top of their list 😉January 27, 2014 at 09:59 #1879January 27, 2014 at 10:33 #1890
Hi, if it makes it clearer, it’s not a problem updating it. Our developers are able to reproduce it in any case 😉
This topic was marked as solved, you can't post.