Forum / NoMachine for Linux / White screen when tried to access a Linux Ubuntu machine from Windows 10
Tagged: headless server linux ubuntu
- This topic has 11 replies, 5 voices, and was last updated 3 years, 7 months ago by Britgirl.
August 30, 2019 at 15:49 #23473cfantonioParticipant
I’m trying to connect to a headless Ubuntu 18.10 machine using Windows 10 but all I get is a white screen, first time worked perfectly asking if I wanted to create a new display but afterwards I was getting a black screen then trying to fix it after reading several forum posts then now I get just a white screen. Log is attached.
Attachments:September 2, 2019 at 09:02 #23478MthContributor
While there is no indication in the logs why there was problem with the session at first,
the white screen is most likely caused by the Login Window screen on Wayland:
2019-08-30 14:43:41 832.519 1068 NXSERVER checkLocalSession: found X server process: [Xwayland /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6]
Currently NoMachine does not work well with Wayland when using proprietary drivers,
or in virtual machines.
In the logs we noticed a standard Xorg server, which should work, but there is no connection attempt.
Please check if disabling Wayland on login window help in this case. Standard
procedure on Ubuntu is to edit /etc/gdm3/custom.conf file and uncomment or add line:
Please let us know if there are any more problems.
/MthSeptember 3, 2019 at 14:19 #23507cfantonioParticipant
I disable Wayland and I got a black screen instead of white, but then I restarted gdm and nxserver and I was able to create a virtual screen, many thanks for the help.
Just a quick question is that I’m having trouble to access root directory, it doesn’t show the authentication screen when running virtual screen on headless server.
Regards,September 20, 2019 at 18:14 #23694MthContributor
Glad to know you can now connect.
Can you explain what you mean when you write “it doesn’t show the authentication screen”? Are you talking about the Login Window screen, or administrator authorization when trying to access the directory? What exactly are you doing?
/MthSeptember 26, 2019 at 08:29 #23757
I am having a similar issue with the latest gnome release, using opensource ati drivers. if the computer screen powers off or goes blank nomachine is unable wake up the display and I see only a white screen on the remote side. This only happens with Wayland, If I disable Wayland the display wakes up as expected. Also this only became an issue with the most recent release of gnome 3.34, it was not an issue with gnome 3.32. I would prefer to use Wayland so I hope this can be fixed in a future release. Happy to include any logs which may be helpful or do further testingSeptember 26, 2019 at 09:31 #23772
jjgalvez, would you provide: your Linux OS distribution, the kernel version, the video card model?
Have you got access to the machine on the server side? What do you see if you try to wake up the screen providing some keyboard/mouse input?September 27, 2019 at 08:15 #23793
Thank you for getting back to me so quickly.
video card: Radeon R7 240 (MSI)
other info: using opensource drivers, DE Gnome 3.34
I have access to the server, when screen is locked and blank, when I try to connect with NoMachine I see a white screen on the client. Nothing happens on the server the screens remains blank. I can wake the server with its keyboard or mouse and the screen opens to the lock screen, which then comes up in the client as well. At this point I can interact with the server again from the client.September 30, 2019 at 10:56 #23825
I think I’m able to reproduce on a similar setup. Going to open a Trouble Report.
Meanwhile, would you try this workaround:
October 9, 2019 at 08:36 #23908
- Edit DisplayServerExtraOptions in /usr/NX/etc/node.cfg in this way:
DisplayServerExtraOptions "-wlmode compositor"
- Restart NoMachine:
- Try to connect to view the desktop. If it fails, edit PAM configuration as described here.
Thank you! Editing the DisplayServerExtraOptions and the PAM config in from su to system-login fixed the issue. You are awesome, Wayland is now working again.October 9, 2019 at 08:37 #23909
BTW this may be something that should be added to the knowledge base.
Again Thank you so muchOctober 9, 2019 at 09:37 #23913
You’re welcome. I’ll open a Trouble Report to track this issue.October 10, 2019 at 09:07 #23938BritgirlParticipant
Here is the Trouble Report’s link: https://www.nomachine.com/TR10Q09420
It also includes the known workaround. Please use the ‘notify me’ checkbox to receive notification of when a patch has been officially released.
This topic was marked as closed, you can't post.