fra81

[fra81]

@dark_sylinc

You don’t work for NoMachine, but it seems like you do! 😉

@hellcats

I’d try the suggestions dark_sylinc rightly provided, starting from toggling hardware acceleration. This can also be done from the Server settings GUI, Performance panel.

[fra81]

Hi,

this is strange indeed. Did you have the chance to verify if this behaviour only occurs when connecting from the Mac? Does using the integrated monitor instead of the external one change anything? And would you run a debug package to gather more information?

[fra81]

Hi Tea,

we reproduced this issue in our labs and opened the following Trouble Report:

https://knowledgebase.nomachine.com/TR04S10193

You can select to be notified when it is fixed. Thanks for reporting!

[fra81]

Hi,

we can’t reproduce this problem in our labs. Can you explain exactly what you see in the video when it doesn’t work? You can attach a screenshot, if you want.

When using WRD, do you connect to the same desktop where also NoMachine is connected (that is the physical display)?

Finally, please make another test. While keeping ‘Use acceleration for display processing’ disabled, edit the ‘C:\Program Files (x86)\NoMachine\etc\node.cfg’ and add this line:

DisplayServerExtraOptions "-nodxgigrab"

Restart the NoMachine server and try again.

[fra81]

Hi,

surely the most recent sessions are the relevent ones. You can send only those or all logs, as you prefer.

[fra81]

Hi Remo,

I don’t see anything abnormal here. Tto reduce the GPU usage, you can try to check the ‘Disable client-side image post-processing’ and ‘Disable multi-pass display encoding’ options in the Display setttings in the session menu panel, but this is not necessarily what you want. To stop the NoMachine player from using the GPU completely, you would need to check instead the ‘Disable client side hardware decoding’ option. At this point the software fallback will be used, though fully optimized.

[fra81]

Hi TimeWalker,

the original FR has been dismissed because the OMX framework, from our tests, revealed to be not suitable at its current state. MMAL is indeed under evaluation by our development team and you are right that it can be an interesting alternative.

[fra81]

Hi Jon,

yes, it could definitely have to do with the settings on the Linux system, but we can check NoMachine logs for any issue. Please find instructions for server side logs at https://www.nomachine.com/DT11R00181#1.1 (debug level, steps 1 and 2, is not necessary) and for client side logs at https://www.nomachine.com/DT11R00181#2.2.

[fra81]

Thank you for reporting!

[fra81]

Hi PRosa,

please try to uncheck the following two options (one at a time) in the Server settings -> Performance tab of the computer where you are connecting to:

Use hardware encoding

Use acceleration for display processing

Does any of them help?

[fra81]

Hi,

the problems you see are not caused by NoMachine and are described in this article:

https://www.nomachine.com/AR03P00973

You may try with a dummy HDMI display adapter or the suggestions at point 2) of the article.

[fra81]

Hi zerocool,

please try to open Server settings –> Performance tab, on the server machine, and uncheck the ‘Use acceleration for display processing’ option. Let us know if that works.

[fra81]

Hi oscahie,

some changes have been done in the new version 7.4.1. Can you try to install it on the server machine?

[fra81]

Hi Coleman,

can you show the output of the ‘xset q’  command run inside the NoMachine session, when the screen is off?

[fra81]

Thanks for the logs. I can see there is a couple of issues that are fixed in NoMachine version 7, even though it’s not completely clear if they are related to the problem you are experiencing. So please upgrade also the server side to version 7 (you are using there version 6.13.1). If the problem is still reproducible, it would be great to have a new set of logs (client + server), so that we can rule out what is not related.

[Author]

Posts