NoMachine server on Rocky 8 not working

[nilsonaj]

NoMachine is working when connecting to one PC with Rocky8, but failing connecting to  another machine.  Both machines were clean installed with rocky 8, and then clean installed latest NoMachine, but I can connect to one and not the other.  The connection appears to start, but then at the client I get error 104.  The video card is different and the sound card is different.

Here is the really odd thing.  Same hardware I installed centos7 and it all worked perfectly.
inside the client logs I see errors like this….
824374 824482 2023-02-24 14:07:52 055.622 ProxySession/ProxySession: ERROR! Session failure in stage ‘StageWaitingProxyVersion’.
Error: Session negotiation failure.
824374 824482 2023-02-24 14:07:52 055.658 ProxySession/ProxySession: ERROR! We possibly provided a wrong version
824374 824482 2023-02-24 14:07:52 055.663 ProxySession/ProxySession: ERROR! or an invalid session authentication cookie.

Attached is the server logs…

[Britgirl]

Hi, hard to say without seeing the logs.

Please submit both Player and Server logs as per the instructions here:

https://kb.nomachine.com/DT07S00244

and send them to forum[at]nomachine[dot]com. Thanks!

[nilsonaj]

I thought I did that already.  How do you associate the email with the problem?

[nilsonaj]

Ok trying again following instructions more meticulously.  I apparently had selected level 6 not 7 when I sent them before.

 

[vhitoc]

Hi,

I have the same problem in Fedora 37 kde plasma, with free version of NoMachine

Please help

[Britgirl]

Nilsonaj, thanks for the additional logs. They indicate a possible issue with Wayland. What DE are you using? Our test on the fly was with Gnome and everything works.

Vhitoc, we would need the server side logs as per the instructions given previously.

However, we are aware of an issue when using KDE when Wayland is the display server. You could try using an alternative desktop environment first maybe? If that doesn’t help, maybe switch over to X.org?

[nilsonaj]

First Thanks for taking the time to look at the logs and answer me.

I am using KDE with Wayland (I assume that is what you wanted to know when you asked about DE), BUT as I said I am using the exact same software combination on other hardware, and it works. (I suppose it could still could be a KDE/Wayland thing)

I have a very controlled kickstart install process, I even did rpm -qa on the two systems and compared the output.

I have tried a bunch of different nomachine settings, and non of them seem to do anything, always the same errors… Do you have any settings combination you might suggest.   Running a different desktop environment is not a good option.

 

 

[nilsonaj]

I see these error messages in a log file of  the failing server… Which I do not see on the “working” server.

I find it suspicious because the video card is different.

xagentShadowInit: ERROR! Unable to shadow a 30 bit display.
Error: Aborting session with ‘(EE) Failed to initialize mirror poller’.
Session: Aborting session at Wed Mar 1 12:50:39 2023.
Session: Session aborted at Wed Mar 1 12:50:39 2023.
Info: Using display buffer for screen updates.
1091524 1443607 2023-03-01 12:50:39 373.025 NXDisplayServer: WARNING! Display application not running [HA].
1091524 1443608 2023-03-01 12:50:39 386.825 NXDisplayServer: WARNING! Display application not running [NA].
1091524 1443608 2023-03-01 12:50:39 386.944 NXDisplayServer: WARNING! Display application not running [KA].
1091524 1443608 2023-03-01 12:50:39 387.896 NXDisplayServer: WARNING! Display application not running [JC].
1091524 1443608 2023-03-01 12:50:39 387.911 NXDisplayServer: WARNING! Display application not running [LA].
1091524 1443607 2023-03-01 12:50:39 429.693 NXDisplayServer: WARNING! Display application not running [NA].
1091524 1443607 2023-03-01 12:50:39 429.725 NXDisplayServer: WARNING! Display application not running [JC].
1091524 1443607 2023-03-01 12:50:39 429.732 NXDisplayServer: WARNING! Display application not running [LA].
1443599 1443599 12:50:39 527 nxexecScreen: ERROR! Dispatch abnormal exit.

[nilsonaj]

For now I was able to start with X.org instead of Wayland, and NoMachine now works

 

[Britgirl]

I had the logs checked again by our Core team. The problem is related to how NoMachine handles 10-bit color displays.

We’ve opened a Trouble Report which you can monitor here:

https://kb.nomachine.com/TR03U10784

The workaround is to use X.org instead.

[Author]

Posts