Issues with NoMachine 9.2.x on Manjaro

[Hadden89]

After the update , it seems that NoMachine is not able to create the display anymore for Manjaro from Windows 11

Connection is correctly established.. but no way to have a working display.

If I try to access windows 11 from the same machine, everything works; same between w10 e 11 machines.

So the issue here is clearly on Linux server, which from what I read is not extremely uncommon.

I’ve already tried some of the tips read, like enabling EGL or switching the display to :10 with no luck.

I’m on KDE Plasma Wayland and don’t have nvidia drivers.

 

[Britgirl]

Hi, can you send us the logs from the server? Go to the NoMachine Settings > Server > Security, scroll down and click the Take logs button. Send that file to us. You can attach here or send it to forum[at]nomachine[dot]com. If you send by email, please us the title of this topic in the subject. Thanks!

[Hadden89]

Hi Brit , thanks for the interest.

I made a typo in the previous post as I’m on X11/Xorg and not on Wayland .

Btw , I’m starting to think my issue was related to a misconfiguration in the swap file , as I started to get some oom (out of memory issue) in system apps in latest day.

So I reinstalled Nomachine from package manager,

then did a new swap file and set the swappiness to 10 (pretty sure the last one fixed the things).

Now I see two desktop, :20 (which is the chrome remote desktop used as fallback)

and :0 which is default NoMachine desktop (which now is connecting properly).

Still can’t transfer between Linux and Windows (the requests appear but deny/allow doesn’t do anything).

Btw, I’ll attach the old log I made before (albeit it still may show errors by missing sudo ./nxserver –useradd Garyno)

Regards.

Attachments:

1. Server-logs-2025-11-08-14.21.25_fault.zip

[Tor]

Hey Hadden, please confirm that you logged in to the remote desktop with the same user currently logged in on the Linux desktop, the so called “desktop owner”. Only the owner can allow or deny a service, so this could be the reason why you can’t do it.

[Hadden89]

Yes, I’m logged as desktop owner.

Btw it turns out that I can actually transfer, but I have to press “allow” 4-5 times then the process start.

If I identify the root cause I’ll update you 🙂

[mattspod]

Once of the things I learnt recently is if you have “Blank the physical screen when somebody connects” then you need to ensure your output has DPMS enabled, if this is disabled per ‘xset -q’ then NoMachine blank screens after authentication, it doesn’t seem to be able to gracefully handle this.  In my scenario the DPMS was disabled some months ago as I tried the kitchen sink and more (systemd entries, gbus entries, some /etc changes) to prevent the NUC ever sleeping so gnome-remote-desktop would always be available – I tried so many things that I probably couldn’t get DPMS enabled if I tried …

[Author]

Posts