bucu

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

[bucu]

Hi,

we have reproduced your problem. We opened a Trouble Report for it. You can sign here (https://www.nomachine.com/TR11R09927) to get a notification once the fix is available.

[bucu]

Hi,

have you tried selecting a diferent resolution from the slider in NoMachine’s display settings? Can you make a screenshot of the resolutions available there? That said, please keep in mind that NoMachine does not support any beta version of macOS.

[bucu]

Hi,

we already have a Feature Request for it https://www.nomachine.com/FR10M02977. You can sign up to receive notification when it is added. That said, if you want to workaround this, you will need to remap keys on the client side. We send modifiers directly to the system so remapping keys on server side won’t affect NoMachine input.

[bucu]

Hi,

we are still investigating your issue. We will update you when we have anything new.

[bucu]

Hi,

the fix made it into the current version however it was tuned for better user experience. We would like to send you a debug package with that tuning reverted to see if it helps with your case. If you are interested please let us know and we will contact you via email.

[bucu]

Hi,

What we suggest is to start from a clean situation, by removing all nxnode entries from “Security and privacy” in System Preferences, in the Accessibility and Screen Recording tabs. Then you should restart nxserver and see if problems are cleared. You should get two notifications about granting nxnode those permissions when reinstalling.

If that doesn’t help we would need logs from server side. To gather logs please follow these instructions: https://www.nomachine.com/DT10O00163. You can then send your logs to forum[at]nomachine[dot]com.

[bucu]

It looks like the problem is on the client side. We have a Feature Request that will solve your problem. If you wish you can sign and get notified when it is added.

[Author]

Posts