Forum Replies Created
-
Posts
-
Hi,
I think you get a point and such option would be useful indeed. We opened a Feature Request to track it:
https://www.nomachine.com/FR01S04065
Thanks for your useful feedback!
Hi,
what you describe is the intended behaviour. On dragging operations NoMachine hides the local cursor and shows the remote cursor instead, so that the cursor sticks to the object that is being dragged. This avoids the effect of the local cursor moving “forward”. At the moment there is no option to disable this behaviour.
Hi,
the flickering is very likely a problem of the video drivers when working headless. You can verify that by leaving the monitor attached when connecting through NoMachine.
Hi,
In order to get either Gnome or Cinnamon to work I have to turn off gdm.
this means that the problem Cinnamon is having is related to the drivers (and graphics card) when running headless and excludes a NoMachine issue. When turning off gdm, NoMachine creates it own virtual display and Cinnamon is run into it, so that it doesn’t depend on the actual graphics card anymore. You may check for alternative drivers or keep gdm disabled or try to plug a dummy HDMI adapter into the server.
Hi,
is there a monitor attached to the board? If not, can you try to attach a monitor and see if the issue persists?
Hi Nem,
I think this Feature Request is what you are looking for:
https://www.nomachine.com/FR02M02864
You can select to be notified when it is implemented.
Hi,
use of software rendering has to be expected on a headless system, but we can’t reproduce any crash in our labs. We would need server side logs to investigate further (see https://www.nomachine.com/AR10K00697). You can send them to forum[at]nomachine[dot]com.
Hi,
it looks like a known issue:
https://www.nomachine.com/TR08R09817
It will be fixed in the next update, so you can select to be notified.
Hi,
please follow instructions in https://www.nomachine.com/AR09L00810 to get a backtrace from the core file. Also server side logs (https://www.nomachine.com/AR10K00697) could be useful. You can send everything to forum[at]nomachine[dot]com referencing this thread.
From what you both say, this looks like a problem with the video drivers rathen than with NoMachine. In one case I see this was fixed by plugging a HDMI, in the other case by rebooting and it is confirmed further by the fact that there is no delay when using the display server provided by NoMachine. In fact some drivers/cards can be fast at rendering but much slower when images have to be pulled back from the GPU. I would try to check for newer versions of proprietary or OSS drivers.
Unfortunately relevant logs are missing. Please select the ‘Don’t delete log files on exit’ checkbox as per instructions. Alternatively, you can gather logs before closing the player window, and even better if you could gather again also the server side logs (while the session is still running), so that we will have matching client-server logs. Thanks for cooperation!
Hi,
we don’t reproduce this issue in our labs. Can you make an example of an effected application?
For a test, please enable the ‘Show remote cursor pointer’ option in the menu panel (https://www.nomachine.com/DT10O00156&dn=menu%20panel#3). Is the remote cursor image rendered correctly?
Hi Elizabeth,
do you mean that you weren’t getting a black screen before the reboot? Is the server a headless machine?
Server side logs look clean. Can you send also client side logs? Instructions in https://www.nomachine.com/DT10O00163#2.
Hi Sean,
NoMachine will always use the same GPU used by Windows to render the desktop. To use the Nvidia GPU you should configure the system to do so. Similarly, NoMachine will offer the same resolutions made available by Windows (depending on the graphics card and drivers). In case the Windows machine you connect to is headless, that could be a reason why the set of resolutions is limited.