bucu

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

[bucu]

The old event API used when setting that key is deprecated and the problem is not on NoMachine’s side so there is little we can do about it.

We would like to hear more about the problem with dragging you have mentioned in the first post. Would you be intereseted in trying out a custom package with debug enabled (assuming we won’t be able to reproduce that dragging problem in our labs)?

As for missing modifiers – it sounds like https://kb.nomachine.com/TR09S10357 can you confirm that this is your problem?

[bucu]

Does the pulsing happen only when using local mouse/keyboard? If yes, then it is an expected behaviour that is meant to show that the machine is not “dead” to a user that is not aware that someone is connected.

[bucu]

Hi,

can you check if any gamma correcting application is running on the server side? It could be f.lux, lunar or something similiar. If they are running you will need to disable them for blanking to work properly.

If that’s not the case we would need server side logs to investigate your problem. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

Hi,

please try to add the following key in the /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg file on the server machine:

DisplayServerExtraOptions "-oldeventapi 1"

Restart NoMachine and see if anything changes.

[bucu]

Hi,

you can try using alternate event API. To do so: append DisplayServerExtraOptions "-alteventapi 1" to /usr/NX/etc/node.cfg on the server side. After that you will need to restart nxserver (sudo /etc/NX/nxserver --restart).

If that doesn’t help we would need server side logs to investigate your problem. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

Unfortunately logs you have sent are from login window not from a session using Awesome WM.
To get proper logs:
1. before connecting with NoMachine make sure that the user is logged in and Awesome WM is running
2. on server side execute: sudo /etc/NX/nxserver --debug --enable all
3. connect with NoMachine to server machine and make sure that the problem is reproduced.
4. on server machine execute: sudo /etc/NX/nxserver --debug --collect

You mentioned you have nvidia GPU. Is the problem present when using nouveau drivers? One more thing we noticed is that the “primary” output is disabled. Can you please remove your randr script and see if with default configuration you still get black screen?

[Author]

Posts