Forum Replies Created
-
Posts
-
Hi, it’s possibly the lossless refinement. NoMachine’s own default settings should be suitable for the majority of environments in order to obtain optimal performance. Nevertheless, in some environments and with particular applications it may be necessary to force specific settings for fine-tuning of the performance and display quality. Try adding this option to the node.cfg file on the server side.
DisplayServerExtraOptions "-refinement 0"Does that change anything?
Hi,
please gather logs from the fedora host, following the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
After that please run
sudo netstat -anlp | grep eglin a terminal and show us the output.Then run
sudo /usr/NX/bin/nxserver --eglcapture yesand reboot.Do you still get the grey screen?
NoMachine works out-of-the-box with headless machines. It does this by detecting that an x server is not running and creates its own. It’s possible that you get a black screen or white screen or frozen screen on Linux when the X server is running but it is not rendering because the system’s video card is turned off (e.g you detach the monitor). In this case NoMachine doesn’t use its own virtual display because it detects that the X server is still running. You should therefore disable the x server first, restart NoMachine server, and then connect with NoMachine.
More about headless Linux hosts here: https://kb.nomachine.com/AR03P00973
To disable the X server permanently for example:sudo systemctl set-default multi-user.targetTo enable it again:
sudo systemctl set-default graphical.targetAfter disabling or re-enabling always restart the nx service
sudo /etc/NX/nxserver --restartHi,
there is a Trouble Report open specifically for Windows 11 about screen-blanking but it affects set-ups where there is a secondary monitor attached, which you have unplugged, so we’d like to investigate further.
https://kb.nomachine.com/TR05T10545
Can you send us the logs of the computer on which you are trying to blank the screen? Please follow the instructions here: https://kb.nomachine.com/DT07S00243 (enabling debug, reproducing the issue, extracting the logs from the server side).
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Check the topic here which was related to Firewalld. Not specifically for Arch but it might help?
We are still investigating but so far the error appears to be caused by dbus not returning the proper connector name for the monitor when it’s locked and put into sleep status. This then causes the issue that you are encountering and the user is unable to connect. We’ll come back to you if we need further information.
I also installed NoMachine on iPad but neither PC nor RPi can be connected.
Please confirm so that we can investigate:
– All the devices are on the same LAN and are visible in your Machines panel. If so, and you can’t connect, what errors do you see?
– Or are you connecting using the IP addresses? If so, and you can’t connect, what errors do you see?Confirm the following:
– From Mac you can connect to Windows
– From Mac you can connect to Raspberry– From Raspberry you can connect to Windows
– From Raspberry you can see and connect to Mac– From Windows you can connect to Mac
– From Windows you can connect to Raspberry– From iPad you cannot connect to Windows – what’s the error?
– From iPad you cannot connect to Raspberry -what’s the error?
– From iPad you can connect to MacNoMachine is designed to work out-of-the-box on Linux headless machines and NoMachine is able to detect when the X server is not running and run its own virtual display, which is an embedded X server. Turning off the monitor on Linux, when before it was switched on (so you force it to become headless), can lead to various symptoms (e.g. black screen or white screen or frozen screen), so you should stop the X server manually first, in order to make NoMachine use its own display service. That way when you get home and connect, you will not see a black screen. Instructions on how to do this are in this article help: https://kb.nomachine.com/AR03P00973.
The issue is possibly related to the following Trouble Report already open and being investigated: https://kb.nomachine.com/TR03V11103. Please use the link to track its status.
I forgot to mention that version 8.16 was released last month (I noticed you are using 8.13), so if possible you should update your installation also because in 8.15 we included two important X.Org and OpenSSL patches for CVE-2024-9632 and CVE-2024-9143 respectively.
Your test proves that the culprit is not NoMachine, so disabling “nxserver for the time being” is not necessary. I’m not quite sure why you want to use NoMachine and the xterm for x-forwarding at the same time but with our Terminal Server products, you could run a custom session to access your python app rather than a desktop session. In any case, this is not the fault of NoMachine, but Gnome. If you try with XFCE for example, you won’t have this problem.