Forum Replies Created
Issue is resolved. I was looking through your KB and found some additional Wayland settings. In node.cfg I uncommented EnableEGLCapture 1 and WaylandModes “drm,compositor,egl” which seems to have fixed the issue. Not sure which one fixed it but since it is working now I am inclined to leave them both enabled as they are.
Server is not a virtual machine, normal desktop. I am using open source video drivers (mesa) the video card is an AMD video card. I will look through the logs for errors and report back
@graywolf – thank you I will wait for the next update
@eric.duveau – Thanks, I used to use lightdm but find that gdm works better with gnome. At the moment version 3.34 is working so I’ll stick with it for the time being.
Thank you for the update. Happy to test any workarounds you may come up with, switching back and forth between gdm 3.34 and 3.36 is pretty simple.
Updated to NoMachine 6.10.12 in the hopes that it would fix the GDM white screen issue, but with GDM version 3.36 I still get a white screen trying to remote into a server that I am not already currently logged into. Reverting back to GDM 3.34 for the time being. Hopefully a more permanent fix or workaround can be identified.
More information: downgrading gdm to 3.34 restores the ability to remote to a machine on the login screen. This is likely a temporary workaround. Still very interested if the logs point to a better solution.
Thank you that worked! it seems that I some how messed up the install when I did that last update. The clean install fixed it. Should have tried that first. Thank you again for a great product and for letting us us home users use if for free! I would not help my mother without you!
Thank you log files uploaded as requested
The log files are too large to send via email. Do you have a dropbox or similar service I can use?
I reviewed the output from the two commands you suggested, and it seems that I am not in the appropriate group. The machine is pretty locked down by our IT department. I was able to run the client by following the instructions on making it portable, but alas I am still not able to connect. I suspect it is a firewall issue on my end. I will try one last thing using an ssh tunnel, but I’m not holding my breath.
Thanks for the assistance but at this point I do think its all on my end
Thank you, yes I have the latest client version from the website, and I am logging in as a domain userOctober 9, 2019 at 08:37 in reply to: White screen when tried to access a Linux Ubuntu machine from Windows 10 #23909
BTW this may be something that should be added to the knowledge base.
Again Thank you so muchOctober 9, 2019 at 08:36 in reply to: White screen when tried to access a Linux Ubuntu machine from Windows 10 #23908
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.September 27, 2019 at 08:15 in reply to: White screen when tried to access a Linux Ubuntu machine from Windows 10 #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 26, 2019 at 08:29 in reply to: White screen when tried to access a Linux Ubuntu machine from Windows 10 #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 testing