Forum Replies Created
-
Posts
-
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.
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.
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.
Hi,
there is one thing you can try as a workaround: on server side open terminal and execute:
xrandr --output OUTPUT --fb 2560x1600 --panning 2560x1600if you have 13″ MBPxrandr --output OUTPUT --fb 2880x1800 --panning 2880x1800if 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.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.cfgadd below line, then restart server and let us know if that changed anything?DisplayServerExtraOptions "-oldeventapi 1"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
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.
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
Hi,
atm I’d recommend unistalling 6.9.2 on the server side and using the patched package 6.8.1. Client side can remain as it is.
Hi,
if your server side machine shows only those resolutions you will have to add it manually. You can follow instructions in this link to add any resolution you need.
We would like to send you a package with a possible fix for slow redraw problem. Please contact us via mail at forum[at]nomachine[dot]com with your linux distro info so we can prepare a proper package for your system.
Hi,
please uninstall your current package and install one provided for debug (nomachine_6.7.6_1.dmg). There is no need to modify the cfg files. Just follow the instructions you received via email.
Thanks for the logs, we were able to reproduce your issue and are currently working on a fix. Will you be interested in trying it out once we have it ready? It should be ready soon after the newest version is released.
Hi,
We can’t reproduce it in our labs. In order to narrow down the problem we would need to send you a debug version for the server side. Please let us know if you are interested in trying it out. If yes, we will contact you via email.