bucu

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

[bucu]

Hi,

there is one thing you can try as a workaround: on server side open terminal and execute:

• xrandr --output OUTPUT --fb 2560x1600 --panning 2560x1600 if you have 13″ MBP
• xrandr --output OUTPUT --fb 2880x1800 --panning 2880x1800 if you have 15″ MBP

Where OUTPUT is your output’s name you can get from xrandr -q (for example VGA-0, LVDS-1). This should set your server’s screen size to Retina’s pixel resolution.

[bucu]

Hi,

we are currently investigating your issue. In the meanwhile could you try to edit NoMachine option file:/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg add below line, then restart server and let us know if that changed anything?

DisplayServerExtraOptions "-oldeventapi 1"

[bucu]

Hi,

macOS when lid is closed does not update the screen content, that’s why Caffeinate is only good for background tasks or ssh. If you don’t want others to see your screen, you can try using screen blanking. You can find more info about this feature here

[bucu]

Hi,

sorry for the late reply, we were investigating ways to mitigate the fact that OS X generates too many scroll events. You must keep in mind that X apps are not designed to handle Magic Mouse or Macbook’s trackapad: they are trying to do a redraw on every scroll event, hence the bad performance.

That said, we have one more tweak that will be added in the upcoming release and we hope it will improve things further. Until then the only thing we can suggest is to use a regular mouse instead of Apple’s mouse/touchpad.

[bucu]

Hi,

we have an experimental feature for adding the possibility to use non standard resolutions on MacOS. If you are interested in trying out a test package with that feature please contact us at forums[at]nomachine[dot]com

[Author]

Posts