bucu

[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?

[bucu]

Hi,

we were not able to reproduce your issue in our labs. We noticed that in some cases cursor shape does not change, but if clicked in correct spot windows would resize. Can you confirm that you tried resizing despite cursor not changing shape and even thought it could be difficult to get?

If you are sure it is not the case then may you please provide us with more details about your setup? Things like GPU model, driver version, is it a virtual machine, or anything that is unusual in your setup that could help us narrow your problem.

[bucu]

Hi,

are you using any apps that might prevent screen from going to sleep mode like Amphetamine? Closed lid on macOS is one of the cases where we don’t expect the session to work if you don’t have any external monitor or dongle connected.

That said we are working on a fix that will allow users with vanilla macOS to close their lids and still be able to connect.

[bucu]

Hi,

Indeed NoMachine is not setting that bit. We added it but it hasn’t change the behaviour for us – in both cases (with and without) VSCode was working as expected. Would you be interested in trying a debug package with that bit set and some logs enabled? If yes please contact us at forum[at]nomachine[dot]com

[bucu]

I was asking whether you had actually forwarded your mouse/keyboard via USB to the server machine. You can read about how to do it in this document (https://kb.nomachine.com/DT06S00218?s=usb#4.3)

However I have the impression that it’s not your case so if possible please send us server and client logs. Instructions on that can be found in my previous post.

[bucu]

We have never encoutered similiar problems. Is it possible that you have your mouse/keyboard fowarded to the sever machine? If this is the case then it is the expected behaviour. If not, we would need logs from both server and client side. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[Author]

Posts