Forum Replies Created
-
Posts
-
“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.
Please update to the latest version. A number of issues with audio were fixed. If you continue to have problems, please start a new topic.
Hi, wow, that’s quite a distance š
This could indeed be useful but of course it depends on whether the target machines respond to the ping or not. We keep track of all network data that an application like NoMachine can ever track, and so it would be a matter of how to make this data more “accessible” to the user and easier to read, and evaluating where and how to make it accessible without interfering with the design of the user-interface. These statistics, however, are at the application level (i.e what NoMachine sends and retrieves).
NoMachine proxy keeps track of the time of round trips, statistics of lost UDP frames, retransmissions, amount of key-frames requested, congestion and bitrate values calculated by the proxy and reported in proxy callbacks etc etc. The actual data about the network and a real estimate of the performance of the network can only be retrieved by analysing the OS kernel and the networking HW (network card, TCP/IP stack of the OS, traversed routers and so on).
What there is available to you already, which sysadmin and network experts will appreciate, is the Statistics section of the NoMachine connection. Please consult this article which gives guidelines on how to interpret this data: https://www.nomachine.com/AR02N00875 (we’re in the process of updating it btw)-
What you should concentrate on is the ‘link’ section which presents the information you would probably be more interested in. The X Protocol section can be ignored š
This FR is available in “virtual desktop sessions” supported in the Terminal Server for Linux products. “Virtual desktop” does not refer to hypervisor technology.
But the flickering problem is still there.
Did you already consult our tips for using Jetson Nano? If not, and you are using Unity, please consider changing desktop environment.
Tips for using NoMachine on NVIDIA Jetson Nano
https://www.nomachine.com/AR02R01074Hi, I’m pleased to know the patch worked šĀ Using an earlier version of NoMachine probably would have produced the same results, so it was just easier if we sent you a working version from the start, at least that way you can use the software again rather than wait for the next maintenance.
Why it happened…. Could it be that you had Win7 set to English and then in Win10 you chose your native French? Maybe that Win10 translates the system username?