Supporting connections to physical desktops running Wayland

ID: FR10N03221 Priority: Low
Products: NoMachine Server Target: 6
Status: Implemented  

NoMachine should support the Wayland display server protocol when users connect to physical desktops on Wayland.

Desktop environments like GNOME shell and KDE Plasma 5.x provide the backend for both Wayland and and recent Linux distributions such as Fedora 25 or later and Ubuntu 17.10 use Wayland by default but maintain the possibility to switch to
When connecting to physical desktops and until this Feature Request is implemented, users are therefore advised to disable Wayland in the display manager configuration.

E.g. in case of GNOME desktop, add the following key to /etc/gdm/custom.conf:


and restart gdm:

systemctl restart gdm


Ref. More information on Wayland:


Notes for NoMachine virtual desktops

Desktop environments like GNOME and KDE provide both the Wayland and backend, making possible NoMachine virtual desktops to work by relying on X11 even when Wayland is the default display server.

If a Wayland desktop is running (e.g. user A is physically logged-in to the machine), however, virtual desktops run by the owner of the Wayland desktop (user A in our example) will display only a black screen.

As a workaround, edit the node configuration file (/usr/NX/etc/node.cfg) and pre-pend the WAYLAND_DISPLAY variable to the command specified in the DefaultDesktopCommand key. For example:

DefaultDesktopCommand "env WAYLAND_DISPLAY=no dbus-launch --exit-with-session gnome-session --session=ubuntu"

In this way all applications started in the NoMachine virtual desktop will use X11 as fallback since they will be unable to connect to the Wayland display.