bucu

[bucu]

Could you clarify what made the problem go away? Was it adding the -nosckgrab key or deleting node.cfg file? If it was the latter do you remember what changes have you done to that file in the past?

[bucu]

Hi,
could you tell us the display size you see in Display -> Change settings tab in the bottom part? Is it any different than the one shown is system settings?
Can you confirm that the window part visible in the session is moving when you move the window on the server machine?
Have you noticed approximately when the problem has started? Was it maybe after a system update?
One thing you can try to change is editing /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on server machine and adding DisplayServerExtraOptions "-nosckgrab" to the end. Then restart NoMachine with sudo /etc/NX/nxserver --restart and see if anything has changed.

[bucu]

Hi,

sorry for the late reply. Did you do any system updates after NoMachine has been installed? Sometimes system updates produce unexpected behaviour with permissions lists. If that is the case please remove all NoMachine permissions (Accessibilty and Screen Recording) and then reinstall NoMachine.

If the problem persist or it happened without a system update involved, we would need server (macOS) side logs.Here you can find instructions on how to get them. Please send them to forum[at]nomachine[dot]com.

[bucu]

Hi Brian/BerndG/nxmac

we would need logs from server side. Instructions on how to get them can be found here. You can send them to forum[at]nomachine[dot]com. If there are any crash reports that have nxnode/nxserver in their name you can send them too (you can find them by opening Konsole app and going to Crash Report tab).

[bucu]

Hi,
can you edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on your mac mini and add this line:
DisplayServerExtraOptions "-nosckgrab", then restart NoMachine (sudo /etc/NX/nxserver --restart) and try to reproduce?

If it’s possible it would be good to know if the problem exists in the desktop version on NoMachine as the client when connecting to that mac mini.

[bucu]

Hi,

I would start by checking if Screen Recording and Accesabilty permisions are set for NoMachine. If they are, you can try to toggle them off and on. After that please restart NoMachine with sudo /etc/NX/nxserver --restart. This command can be used to get prompts for those permissions if there was no NoMachine entries on those lists. Another thing to check would be making sure that macOS Screen Sharing session is off when trying to connect with NoMachine.

If that doesn’t help can you try installing NoMachine on your MacBook and tell us if the black screen is there too? If yes, then can you try connecting any kind of monitor to your mac mini to check if the image is there after connecting? If none of that helps we would need logs from server side. Instructions on how to get them can be found https://kb.nomachine.com/DT07S00243. You can send them to forum[at]nomachine[dot]com.

[bucu]

@shea @bugizozi

you can also try using an experimental option that can be set in /usr/NX/etc/node.cfg file on the server side. Add this line to that file: DisplayServerExtraOptions "-customresolution 1" then restart NoMachine with sudo /etc/NX/nxserver --restart and after connecting go to Display Setting panel in NoMachine player, toggle “Use custom resolution”, type wanted screen size and press Modify.

[bucu]

Hi,

this should help: please add this line to the /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg file on your MBP machine:

DisplayServerExtraOptions "-eventdelay 0"

Then restart the NoMachine server.

[bucu]

No, they shouldn’t. We are aware of this problem and it will be fixed in next release.

[bucu]

Can you tell us if any of power saving options regarding display from Lock Screen tab in System Settings on your macOS are set? If yes can you please try running this command:
sudo mv /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib-bak
and then restart nxserver with: sudo /etc/NX/nxserver --restart and let us know if anything has changed?

[bucu]

Hi,
we have reproduced your problem. Can you try editing /usr/NX/etc/node.cfg on your server machine and adding DisplayAgentExtraOptions "-alteventapi 1" to its end? After that please restart nxserver with sudo /etc/NX/nxserver --restart. Please let us know if this fixes scrolling in Tixati for you.

[bucu]

I wasn’t precise enough when asking about scaling: I didn’t mean cursor scaling alone, I meant scaling in the system display settings. Can you please clarify that maybe with a screenshot?

That said, we couldn’t reproduce your problem in our labs. Can you send us zipped logs from following folders on the server side while the problem occurs:$HOME/.nx from linux or %USERPROFILE%\.nx from Windows?

Please send them to forums[at]nomachine[dot]com

[bucu]

I assume macOS is the client, what is the server machine you are running your session on? Is there any system display scaling enabled there? Are you, by any chance, running a nested session (you are connected to a server and have opened a new connection from that server)?

[bucu]

Hi,

can you tell us what macOS and NoMachine versions are you having this problem on?

[bucu]

Hi,

it looks like after update the permissions for Accessibilty and Screen Recording are not handled properly. May you please try removing NoMachine from both lists and then restart NoMachine (you can do it from terminal with sudo /etc/NX/nxserver --restart) and follow the prompts that should direct you to enabling both permissions?

[Author]

Posts