Forum Replies Created
-
Posts
-
Hi, RPi4 as a desktop client most likely is not the best choice. If you’re using it to run a Youtube video, for example, with Raspbian’s own Chromium, CPU usage can reach 100%.Ā Whereas if you use a PC to connect, there are no issues whatsoever. We are planning to support GPU accelerated decoding on RPi in the future, so watch out for that.
Adding support for GPU accelerated H.264 hardware decoding on Raspberry devices
https://www.nomachine.com/FR10R04038Possibly because something changed in Gnome on Ubuntu 20.04? If you Google, other users are having unlock issues without NoMachine.
What you need is NoMachine Network. This is an upcoming feature to help users with set-ups like yourself connect without having to know the IP address or when port-forwarding on the router is not possible.
https://www.nomachine.com/FR07J02731
Port-forwarding can be configured using the instructions here:
How to connect to NoMachine when the server is behind a NAT router or a firewall
ttps://www.nomachine.com/AR11L00827“Iām being told that the Avid project must be made smaller to keep NoMachine working well” – who is “they”? š
Indeed, how can a separate Avid server host affect NoMachine performance?
Is this the same environment as you wrote at the start? If so, I will split this as a new topic about black screen on Arch with KDE.
If the flickering has gone, then leave you’re NoMachine settings as they are š You’re better off contacting the nvidia developer forums for the other issues.
how to switch automatically the mouse cursor from the ubuntu / jetson nano / os to the Windows 10 / NoMachine client OS and viceversa, automatically without to press a shortkey combinations of keys.
What do you mean? Have you enabled “Grab the mouse input”? If so, the only way to unblock the “grab” is by using the keyboard shortcuts, in this case Control+Alt+Click.
Sorry to hear that the problem persisted. We test our software on thousands of machines with thousands of different desktop environments and Linux versions, in their original factory settings, but of course we can’t guarantee that it will work on every computer out-of-the-box with the multitude of custom settings that our Linux users have configured. Next time, send us the logs from the affected computer.
The previous behaviour was that when I log in, it gives me remote access to the logged in session (same user).
And this is still the case. However, I’m not sure what version you are referring to and whether you were using the NoMachine for Linux free version or possible our legacy product NX Free Edition. If you’re interested in running virtual Linux desktop sessions, you should try the Workstation product from our For Enterprise range. Next time, what I strongly suggest is to be sure you removed all residuals of version 3 you had before, if any, and this extends to any NX derivatives you may have been using since these are not from NoMachine. We’ve seen NX installations from products using our open-source software failing to uninstall correctly and interfering every attempt of NoMachine to run on the same computer later.
Please update to the latest version on both client and server sides and tell us if you are still having issues with audio.
I doubt this is related to NoMachine, nor Google Cloud, and that the problems are still there even without NoMachine installed! Given that you mention svchost.exe process memory becomes high which is known for causing similar memory problems, try checking this article: https://www.wintips.org/how-to-fix-svchost-exe-netsvcs-memory-leak-or-high-cpu-usage-problems/
No logs were received so this topic will be closed. Please update to the latest version available on the website and let us know if this is still occurring.
Please update to the latest version of the software and let us know if this issue is still happening. In that case, open a new topic š
Can you update to the latest version and see if you can replicate the behaviour? Extract the debug logs as mentioned before and resubmit.
Connect with ssh and:
sudo /etc/NX/nxserver --history | grep Connected sudo /etc/NX/nxserver --disconnect <session ID>or even:
sudo /etc/NX/nxserver --restartYou could also try connecting from another device.