Tagged: endless login
November 12, 2018 at 10:06 #20424xcjiangParticipant
Server: Ubuntu 18.04
Client: Windows 7
NoMachine: latest version
When a monitor is connected, NoMachine works fine. But after removing monitor, NoMachine shows nothing but a blank window.
Trying to exec “sudo /usr/NX/bin/nxserver –restart” but nothing changed.November 12, 2018 at 13:43 #20433BritgirlKeymaster
Can you follow the advice given here and let me know if it helps?
How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973November 13, 2018 at 08:39 #20439xcjiangParticipant
Yes, it helps. after stopping gdm and restarting nxserver, everything is OK now.November 14, 2018 at 08:57 #20465
I had a similar problem but with bad result. Started desktop (Ubuntu 18.04.1, GNOME3.28) without switching on monitor and without logging in. Accessed remote desktop from laptop (Mint 18.3, Cinnamon). After some mouse clicks got logged in with an Ubuntu screen without launcher and without system tray. I could not do anything on the remote host including logging out. So I went to the desktop and tried to login locally. But got an endless loop: each time I entered my password (correctly, for I could read it after choosing “show text”) I got the login screen anew. Logging in in tty2 goes well.
I tried all the tips on the internet to circumvent this problem with no avail. After a full day of searching the internet and trying out all the suggestions I am desperate.
Please, can anybody give me some clues as to how tackle this problem? I need my desktop now so I will be very graceful!
NoMachine versions: desktop (remote) 22.214.171.124; laptop (client) 5.2.11_1November 16, 2018 at 12:16 #20487
EDIT: I continued my search. In tty2:
~$ ps -ax |grep ssh
1533 ?Ss 0:00 /usr/bin/sshd -D
2076 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin im-launch env LD_PRELOAD=libgtk3-ncsd.so.0 gnome-session — session=ubuntu
8576 tty2 0:00 grep –color=auto ssh
#So 2 processes are running out of tt2. I killed proces 2076:
~$ sudo kill -9 2076
~$ ps -ax |grep ssh
2076 ? Zs 0:00 [ssh-agent] <defunct>
9040 tty2 ……..
~$ ps axo stat,ppid,pid,comm |grep defunct
Zs 1962 2076 ssh-agent <defunct>
# so, 1962 is the parent process which did not stop the child 2076
~$ sudo kill -9 1962
# now I can login at tty1 in the GUI, but I have to do this exercise each time I will login to my desktop.
I am looking for further help, please, to definitely solve this problem. Thnx in advance!November 16, 2018 at 12:17 #20499
I did not succeed to find details of the cause of this inlog blockage. So as a last means I remove NoMachine from the server computer. Now logging in was no longer a problem. Subsequently I reinstalled the newest version and also no problem occurred. In the future I will be aware of the special situation of not being logged in in the server and will avoid it.
As for my problem this thread can be closed.November 16, 2018 at 13:15 #20506BritgirlKeymaster
@Carolus, you were using an old version of the software which handled headless machines only on Enterprise Desktop and not on the free version. From version 6.0.66 the same implementation was included in the free version, and it is possibly for this reason you don’t see that behaviour now you have updated the software.
Please see https://www.nomachine.com/TR11O08272 for more information.
This topic was marked as solved, you can't post.