

To do so, edit the key PhysicalDisplays in /usr/NX/etc/node.cfg: DISPLAY :10 and it will ignore the existing X session on DISPLAY :0 (standard setup in Arch Linux) and start a new virtual session for the remotely connecting user. However, it is possible to setup NoMachine to check only for a particular DISPLAY, e.g.

This may be unwanted, because no other user may use the target computer locally at the same moment and because any person with physical access to the target computer can see on the physical display, what the remotely connected user is doing. In default setup, the Free edition of NoMachine connects the client directly to an existing X session on the remote computer, even if it runs the X Display Manager only. Separate NoMachine X session in parallel with existing X session for MATE desktop environment:ĭefaultDesktopCommand “/usr/bin/mate-session” To resolve this issue, edit the key DefaultDesktopCommand in /usr/NX/etc/node.cfg. This fails in Arch Linux (you get only a black screen) because an Xsession script does not exist. If no X server is running on the server, NoMachine starts its own X server (DISPLAY :0) and tries to run a /etc/X11/Xsession script to get the user into the default DE.

After starting this thread ( Remote Desktop Server: Best choice from official repo or AUR on Raspberry Pi 4 (4 GB RAM)? ), I installed nomachine from the AUR on 's recommendation, and had no issues with it while I also had a monitor plugged into the Pi.
