White screen after first connect since v8

[Coleman]

Hello,

I’m running NoMachine on a Intel based laptop using h.264 hw accel. This past week I saw the update prompt to go to version 8, which I accepted. Since then, there’s a really strange behavior- I can only connect and see the desktop one time. After I disconnect, when I try to connect again later, the connection goes through, but I only receive a white screen.

If I restart the NoMachine service, I am able to connect again fine, but again, only one time. The machine is running Manjaro, and the update to NoMachine shows 8.0.168.

I saw some old posts from around 2020 that seemed to have similar issues, which disabling client side hw decode seemed to workaround the problem, but that doesn’t appear to have any affect here.

Thank you!

[eugenez]

Hello.

I confirm of this behaviour. When connecting to a computer running Manjaro Linux with nomachine version 8.0.168-1, immediately after restarting the nxserver service, the connection proceeds normally. After disconnecting, when reconnecting, we observe a white screen, and, later, the message “connection timed out”.

Next connection to remote desktop becomes possible only after executing “systemctl restart nxserver”.

[shimikano]

I’m witnessing the same behavior on Arch Linux with Intel graphics, Gnome 42.4 on X11 , physical display, NoMachine 8.0.168 installed from the AUR:

The first connection after a server restart works fine, but any subsequent connection results in a white screen. I tried various clients, which clearly points to a server problem.

Disabling hardware encoding on the server solves the issue.

I also tried a fresh NoMachine DEB install on a Ubuntu live CD on the same machine and the same configuration (i.e., hardware encoding enabled). In that case, multiple successive connections work fine.

So, I would say it’s a server configuration issue specific to Arch and hardware encoding with Intel graphics.

[eugenez]

Disabling hardware encoding on the server solves the issue.

Confirm, this solution works fine.

[fra81]

Hi,

would you reproduce the issue again with hardware encoding enabled and send server side logs to forum[at]nomachine[dot]com? Please find instructions in https://kb.nomachine.com/DT11R00182.

[Coleman]

I have sent the requested logs in.

 

[Coleman]

I didn’t see a mention of it in the release notes, but 8.1.2 update that just came out seems to have resolved this problem for me.

 

[Britgirl]

It’s hard to know. Your logs didn’t show anything unusual and we also didn’t change add or fix anything in the latest release that would lead us to believe that it could have been related. We weren’t even able to reproduce the same problem that users here have described. But I’m glad it’s solved for you 🙂

[TimeWalker]

Hi there, it seems like I’ve been suddenly hit with this issue as well. I didn’t have issues before but it’s possible that one of the libraries or drivers on Arch itself upgraded which breaks the system.

I have send a mail with the logs to hopefully help me find the issue.

[Britgirl]

Hi Timewalker, sorry for the delay. The logs you sent actually show that you have hardware encoding enabled on the server side. Please try disabling it, this worked for the other users. On the server, go to Server -> Settings -> Performance and untick the “Use hardware encoding” box. Restart the server and try and connect again. Another thing I should point out is that NoMachine uses the native AMD encoder, not the VA-API, so there could be some misconfiguration in the system perhaps?

[Author]

Posts