Note that when I ping my Ubuntu server in this state I still get fast responses (<1ms) so it’s not the connection. Ok, so I left NoMachine running in the background, still connected to the Linux machine. Killing the NoMachine processes manually on the server But this is very annoying as I lose my current setup.Ĭhange the codec being used by NoMachine on the server The major drawback of these is that they utilise a built-in X server of nxagent, which originates from the year 2005 and.
There are derivatives based on core NX libraries like FreeNX and X2Go. Until version 3.x, NoMachine was known as NX and available under GPL. So what I have to do is restart my Ubuntu machine and then it works flawlessly again. NoMachine enables you to access a graphical desktop of a computer over the network. You may try to use a different version of the drivers, but I can’t say if that will solve the problem. This is an issue on the video card/drivers side. I have seen other similar cases where the local X server is slow to pull pixels data back from video memory. What happens is that after waking the Ubuntu machine up sometimes the connection becomes extremely slow (each command I send takes more than 3 seconds to actually execute). You should start with the local system, stop all unnecessary apps running on the system, do not use VoIP while use VNC or NoMachine. After excluding hardware encoding, GPU is not used by NoMachine directly. Both the machines are here at my house at the same network. I then wake it up using Wake-on-lan and connect through NoMachine. However, since I don’t like leaving my computer turned on at night I use the pm-utils lib to either hibernate or suspend my Ubuntu machine. I connect from the Windows computer to the Ubuntu. NoMachine server on an Ubuntu 20.04 machine. Hey, I’ve been using NoMachine for a few weeks now and I have this annoying problem.
0 kommentar(er)
