bucu

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

[bucu]

Topnotchprincess

is the black screen present also with different WM?

For further investigation we would need a new set of logs from server side. Please make sure that you are connecting to the user’s session (not the login window one). You can follow this link to be sure you get all the logs.

[bucu]

@Topnotchprincess

Hi,

can you provide us the output of the “xrandr -q” command on server side? Have you tried lowering the screen resolution before connecting with NoMachine? Lastly – does Awesome WM supports scaling like @chiao has described?

[bucu]

Can you please try pasting into the terminal with a combination of Ctrl+Shift+V? Some terminal apps use Ctrl+C/V as their inside commands and clipboard is handled by another one (usually by adding Shift key, but it might vary depending on the terminal you use). In addition have you tried pasting with the middle mouse button?

[bucu]

Hi,

the new problem you described is indeed the result of using that option – some applications use relative coordinates while dragging. We will try again to reproduce your problem and find a fix. If we do, we will let you know in this topic.

[bucu]

Hi,

yes – that option was added in 7.7.4. Please try it out and let us know if it made any change.

[bucu]

Hi,

we recently released a new version that has an option that might help you. May you please edit node.cfg file located in /Applications/NoMachine.app/Contents/Frameworks/etc/ on the server side and add this line to it:

DisplayServerExtraOptions "-relativecoords 0"

You will need to restart NoMachine server (sudo /etc/NX/nxserver --restart in terminal) after that, for the changes to take effect. Please let us know if that helped.

[bucu]

Hi,

Can you please do a recording of your session while reproducing the problem with the on-screen keyboard visible on the server(mac) side?

See below the instructions on how to enable onscreen keyboard:
Turn it on: On your Mac, choose Apple menu > System Preferences, click Accessibility, click Keyboard, click Accessibility Keyboard, then select Enable Accessibility Keyboard.
You can also turn on the Accessibility Keyboard by clicking the Input menu in the menu bar, then choosing Show Keyboard Viewer.

[bucu]

Hi,

have you tried disabling and then enabling permissions for NoMachine in Security settings (both for accessibility and screen recording)? If that doesn’t help you can try the workaround from https://knowledgebase.nomachine.com/TR08S10329

If none of that help we would need a full set of logs from server-side. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

Hi,

what you describe sounds very weird. We would like to send you a debug package to investigate the issue further as we couldn’t reproduce it in our labs. If you are willing to try it out please contact us at forum[at]nomachine[dot]com adding the topic title as the email subject.
As a workaround can you try adding DisplayServerExtraOptions "-oldeventapi 1" to your node.cfg on server side? It should be located in /Applications/NoMachine.app/Contents/Frameworks/etc/. After adding it you should restart the nxserver for it to take effect (/etc/NX/nxserver --restart command).

[bucu]

Hi,

your problems looks like the one that was solved in the last release (https://www.nomachine.com/TR10R09842). Are you using the latest package on macOS side? If yes, we would need server side logs to investigate further. If no, can you try it?

To get logs follow this link: https://www.nomachine.com/AR10K00697. When gathered please send them to forum[at]nomachine[dot]com referencing this thread.

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

[Author]

Posts