- This topic has 6 replies, 2 voices, and was last updated 9 months ago by
.
-
Posts
-
I am running a fresh install of Fedora 41 with GNOME 47, Wayland, embedded AMD graphics. After installation of 8.15.3, on the next reboot, the gnome-shell process pegs one of my CPU cores at 100%. This is regardless of whether nxserver or any NoMachine-related service is running, regardless of login session status, etc. There are no log entries for any GNOME service, nor NoMachine, in journalctl or NoMachine’s text logs, that seem to indicate a Wayland, graphics driver, or other issue. For completeness sake, I have tried disabling all hardware acceleration settings in NoMachine server, and also tried disabling EGL as I’ve seen in some other threads in the past. The fact that this CPU usage happens even with the NoMachine services stopped seems to indicate that it has to do with something NoMachine installs into Wayland/X/GNOME, rather than the NoMachine services themselves. As soon as I uninstall NoMachine, on the next reboot, CPU usage returns to normal. Anyone have suggestions on where to look or try next?
Please check the following Trouble Report. Your issue looks very similar to that.
High CPU usage when installing NoMachine v8.15 on Ubuntu
https://kb.nomachine.com/TR01W11263As a temporary workaround, execute in a local terminal:
sudo /etc/NX/nxserver --eglcapture noRestart the desktop manager or logout from the desktop and login again.
Yup, that was it. I thought I had disabled EGL capture in the config files. But doing it with that command resolved it. Thanks.
Thanks for confirming. Developers have already found the cause and implemented a patch. The fix will be released in the next software update.
Sounds good. I was going to follow up and note that with EGL disabled, connecting to an existing login session is much slower but eventually connects, and connectivity completely fails when there is no current session and you’re trying to connect to the GDM login screen. Though it looks like for my purposes, EGL will be fixed soon-ish.
The latest 8.16 provides a patch for this. Please update your software.
This topic was marked as solved, you can't post.