White screen after updating to latest version

[obones]

Hello,

I’m using NoMachine to connect to a KDE 6 desktop which initially was X11 based.
I moved to Wayland and NoMachine continued to work properly.

Just yesterday, I updated to version 9.2.18 and suddenly, all I get is a white screen and after a while a disconnection.

In /usr/NX/var/log/server.log, I see this:

2219502 2219502 2025-12-16 11:57:16 995.050 NXSERVER Session start state machine: Transition from ‘connect’ with event ‘connected’ is ‘sessionRunning’.
2219502 2219502 2025-12-16 11:57:16 995.083 NXSERVER Session start state machine: Handling state: sessionRunning.
2219502 2219502 2025-12-16 11:57:16 995.115 NXSERVER __get_request_from_node [1]
2219502 2219502 2025-12-16 11:57:16 995.144 NXSERVER NXPingManager: Time between pings from the node: 75.
2219502 2219502 2025-12-16 11:57:16 995.174 NXSERVER NXPingManager: Timeout for ping after request: 120.
2219502 2219502 2025-12-16 11:57:16 995.235 NXSERVER Add to the selector node stdout:50
2219502 2219502 2025-12-16 11:57:16 995.278 NXSERVER Added server’s socket: FD#45 to the gSelector.
2219502 2219502 2025-12-16 11:57:16 995.311 NXSERVER Global selector: FD#45 already added.
2217948 2217948 11:57:34 035 nxexecPAMCloseSession: Pam transaction must be provided
2219502 2219502 2025-12-16 11:57:34 039.267 NXSERVER Something to read on FD#50 (__get_request_from_node).
2219502 2219502 2025-12-16 11:57:34 039.336 NXSERVER NXNodeExec: Read from node stdout FD#50.
2219502 2219502 2025-12-16 11:57:34 039.469 NXSERVER Handling code 1004 with function handle_message_node_end_error_simple.
2219502 2219502 2025-12-16 11:57:34 039.535 NXSERVER Cannot find node assigned to socket FD#50.
2219502 2219502 2025-12-16 11:57:34 039.569 NXSERVER ERROR! Received error message from node ‘localhost:4000’, ‘La dernière opération a échoué.’.
2219502 2219502 2025-12-16 11:57:34 039.639 NXSERVER NXUdpControl: Udp range of ports: 4011-4999.
2219502 2219502 2025-12-16 11:57:34 039.662 NXSERVER NXUdpControl: Udp range of  ports from ‘4011’ to ‘4999’.
2219502 2219502 2025-12-16 11:57:34 039.975 NXSERVER NXFile: ‘/usr/NX/var/db/ports.lock’ exists.
2219502 2219502 2025-12-16 11:57:34 040.003 NXSERVER NXFile: ‘/usr/NX/var/db/ports’ exists.
2219502 2219502 2025-12-16 11:57:34 040.051 NXSERVER NXFile: ‘/usr/NX/var/db/ports.lock’ exists.
2219502 2219502 2025-12-16 11:57:34 040.120 NXSERVER Previous message repeated 1 time
2219502 2219502 2025-12-16 11:57:34 040.133 NXSERVER NXOpen FD#30 – file /usr/NX/var/db/ports.lock with mode 1089 and permissions 420 from main::lockFile.
2219502 2219502 2025-12-16 11:57:34 040.170 NXSERVER nxflock: libnxh::NXFileLock(30, 1) returned ‘1’.
2219502 2219502 2025-12-16 11:57:34 040.208 NXSERVER NXFile: ‘/usr/NX/var/db/ports’ exists.
2219502 2219502 2025-12-16 11:57:34 040.252 NXSERVER NXOpen FD#31 – file /usr/NX/var/db/ports with mode 0 and permissions 0 from NXUdpControl::freePort.
2219502 2219502 2025-12-16 11:57:34 040.402 NXSERVER NXFile: ‘/usr/NX/var/db/ports’ exists.

As you can see, it connected at 11:57:16 and somehow stopped at 11:57:34, giving me 18 seconds of whitescreen.

I did see various messages in these forums, but they all mentioned an issue with Wayland that was fixed in version 9.0 which is way before the 9.2 that I’m using.

What am I missing?

[Britgirl]

Hi, we just released 9.3. Could you update first and try to reproduce the problem? If you do, we’ll need to see the logs to be able to understand better.

To do that go to the target machine, in Settings > Server > Security , set the logs to debug level (you have to scroll down in the Security panel), restart nxserver, reproduce the problem and then “Take logs”. Share that entire file that you save. For full instructions, please see here: https://kb.nomachine.com/DT08U00298#1.

The system logs from journalctl would be useful as well. You can attach the files here, or send direct to forum[at]nomachine[dot]com. Thanks!

[Author]

Posts