Forum Replies Created
-
Posts
-
The release of this feature has not been scheduled yet, but you can track it here and also decide to be notified:
Hello,
as you noted, on headless machines it should be possible to set any resolution. We are trying to reproduce your issue in our labs. We will be back to you!
Sure, the patch will be included in the next release! Thank you for letting us know.
You can check here to be notified when the Trouble Report will be closed:
Thank you for the info. Actually they exclude that your are experiencing the same problem we had found (and that will be fixed anyway in the next release). In fact from our observations the problem we found has a very limited impact.
Unfortunately we are not able to reproduce any further problem on any of the machines we tested on. Is it possible that the regression you observed is triggered by a system update? Could you maybe try to uninstall the present version and try version 5.0.47 again in order to see if you get the same results?
Another possible explanation is if you had enabled the H.264 codec with the previous version by installing the NoMachine AVC Pack or by compiling the encoding library by hand. Is this a possibility?
Please also take a ‘sample’ of the process that is consuming the CPU. You can find the option to take a sample in the Activity Monitor utility.
Should I assume that you are running the Java application in a custom session in ‘floating window mode’? In that case the rendering is delegated to Xquartz, and so it actually depends on the Xquartz implementation. In virtual desktops instead the rendering is handled internally by NoMachine and so it is platform independent. Work on removing such dependency from Xquartz in floating window sessions is something we have already in our development roadmap.
Hi,
you might be missing to set ‘EnableDisplayServerVideoCodec 1’. Also restarting the server (‘/usr/NX/bin/nxserver –restart’) could be necessary. However you can use the graphical interface to do those settings:
Click on the NoMachine tray icon -> Show the server status -> Server preferences -> Performance tab
Dragging the app to the trash (and emptying the trash) is enough for a complete uninstallation. You mean that you reinstalled by using directly a 5.0.58 package?
Can you please send the output of this command:
$ ls /Applications/NoMachine.app/Contents/Frameworks/lib/
We managed to reproduce the issue in our labs and we are working on it. It seems it is triggered by the software update process. Please check if uninstalling the software and proceeding with a fresh install solves the problem.
Your server should have dumped a core file (if enabled to do so) in the user’s home directory. Please locate it and get a backtrace from it as per these instructions: https://www.nomachine.com/AR09L00810.
Also it would be useful to know the screen data acqusition method the node is currently using. To do so please gather the logs by following the instructions in https://www.nomachine.com/DT07M00098.
You can send them to forum[at]nomachine[dot]com.
At the moment there is no configuration in NoMachine for selecting a specific GPU. Doesn’t Nvidia settings software allow to assign a GPU to applications in your system?
Can you tell us something more. Are you using this system as a client or a server? Are you concerned about accelerated encoding/decoding?
Hi all,
we would need the diagnostic reports requested by Britgirl to confirm it is the same problem described in the Trouble Report. If you are willing to test the possible fix for this issue, please contact us to forum[at]nomachine[dot]com.
Hi mopac!
Do you have NoMachine version 5 installed? Connecting to headless machine should work out of the box thanks to this implementation:
https://www.nomachine.com/FR10L02842
If you have this problem with version 5, please gather server side logs as exaplained in https://www.nomachine.com/DT07M00098 and send to forum[at]nomachine[dot]com.
Greetings
It is not possible at the moment, but it is something we are working on. It will be possible to encode a single monitor or even a portion of the remote screen selected by the user.
Hello,
thank you for reporting and for the very accurate analysis!
We have reproduced this issue in our labs and opened a Trouble Report to track it:
Thank you for letting us know!
The patch will be released with the next update.
You can track the status of this Trouble Report here: