Forum Replies Created
-
Posts
-
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.
Hi,
the crash report you’ve attached indicate the problem is with physical session only. Can you clarify what did you mean by “virtual”? Did you mean headless or an actual virtual session?
Hi,
we would need some extra info to investigate further:
1. What is the client machine OS?
2. Keyboard type and layout (or anything that is special about it).
3. Can you clarify what does “restart client” mean? Do you have to restart the client machine, or NoMachine Player alone?
4. Is that stuck fn key on the server or client side? Screenshot suggests server, but you seem to imply that it happens on client side.
Hi Darek,
can you tell me more about your setup: what OS is on the affected machine and what NoMachine version are you using? Is the image being refreshed on those not blanked monitors when connected?
Logs from server side might be useful too. To gather logs please follow these instructions: https://www.nomachine.com/DT07M00098 (if you are using v. 5) or https://www.nomachine.com/DT10O00163 (for v. 6)
You can send your logs to forum[at]nomachine[dot]com.
Hi wmacgreg,
we were able to reproduce your problem. We’ve opened a Trouble Report here: https://www.nomachine.com/TR01Q09112. The fix should be included in the next update.
Provided you’ve followed the instructions in the article correctly H.264 will work. The alternative is to use AVC pack which will do all the configuration and libs set up for you, out of the box.
Either way, the only way we can get an idea that you’ve set up everything correctly is with the full set of logs. Instructions were pasted above. Note that the statistics I have asked in the beggining are not the same as logs from server and client side. Please include the top.out file as well.