Forum Replies Created
-
Posts
-
Hi @Gega,
thank you for the reply. I believe some of the issues I was having may have been because of a misconfiguration on my end. After some complete removal and reinstall it seems to be working. I will hold off until the next release in a few weeks and post back if I continue to have issues.
Again thanks
Just installed 7.0.211 on Arch gnome and the tray icon no longer comes on at start. I have to start player first manually. This worked with 7.0.209.
Interesting observation. Setting GDK_BACKEND=wayland in /etc/environments prevents NoMachine from starting properly.
Wanted to provide an update to this topic. It seems that NoMachine is again running under with Wayland gnome on Arch. Since there has not been a NoMachine update I’m assuming that it was some form of gnome regression that caused the issue. To verify I did a complete fresh install of NoMachine removing all my old configurations and it worked out of the box. My current configuration is as follows:
NoMachine: 6.12.3
DM gdm: 3.38.2
DE gnome-shell: 3.38.2
composter mutter: 3.38.2thank you for the reply. NoMachine still not con not detect my wayland display. I do not have any wayland extensions it is just the standard install. I also completely removed NoMachine and reinstalled (mainly to make sure I had not done something goofy to the config files that I didn’t remember).
With both the out-of-the-box install and with the DisplayServerExtraOptions set to “-wlmode composter” NoMachine can not detect my display, nor can it create a new wayland display.
Trying to create a new server shows the attached error.
OS Arche
DM gmd 3.38.1
DE gnome-shell 3.38.1
composter mutter 3.38.1
display server wayland 1.18.0Additional information: Also note that if the user is already logged in NoMachine still creates a new session, but I just get a blank screen. I’m assuming that is because this is the free version which does not support multiple sessions? As stated before If Wayland is turned on NoMachine can not find a display. Disabling Wayland allows it to find and connect to the running display.
Thank you for the reply. The workaround you provided kind of helps. So now when I try to connect to the sever I still get an error saying:
Cannnot detect any display running, Do you want NoMachine to creat a new display and proceed to connect to the desktop?
Selecting yes creates a new XOrg session. I still can not connect to the running Wayland display nor connect to the existing Wayland session. Also I must logout of the NoMachine session to log back into the server locally.
At this time running XOrg seems like a better workaround, Hopefully a solution that allows connecting the WayLAnd display can be found.
Additional information: This seems to be an issue with Wayland. If I switch to XOrg nomachine works as expected, but if I am running Wayland NoMachine is unable to find a running display. Hopefully a workaround which will allow me to switch back to Wayland will be found. If I can provide any additional logs or help troubleshoot this please let me know.
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.