• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

Raspberry Pi: Ultra-high CPU usage on Ubuntu 24.04 ARM + NoMachine

27th January 2025 - Written in: linux

Greetings friends, I have recently upgraded my Raspberry Pi 4 to the latest Ubuntu 24.04 LTS, thinking that it should be stable enough, and solid. But right after upgrading, during the evening my Grafana kiosk mode, which is the whole purpose of this Raspberry Pi, was frozen.

What it was worse, the Raspberry Pi was really hot, and I could see the last temperature metrics from the unit before got into this stuck mode, probably due heat.

I could not find a motive, and I thought it was maybe something anecdotic, so I restart the unit. Jos to my surprise to find it today again on the same state, after a truly high temperatures for the last hours as you can see in the above image.

htop to the rescue

Running a quick htop point me to an staggering 100% CPU consumption by the process /usr/bin/gnome-shell, which for our misfortune it is related to the whole desktop environment. As this was not happening before the upgrade, one could think it was just some buggy gnome package, but an apt-get update && apt-get upgrade didn’t come with any new package or update.

Entering NoMachine

NoMachine TR01W11263 – High CPU usage with NoMachine v8.15 on Ubuntu

Just added the 21st of January, a few days ago at the time of writing this blog post. The guys from NoMachine wrote this known issue for users on Ubuntu 24.04.1 LTS ARM on Raspberry Pi. This is important because I am having the same Ubuntu version on the Jetson Nano and it is working without any issues, so it might be just for Raspberry Pi ARM version for some reason.

There is a few simple steps to resolve this:

sudo /etc/NX/nxserver --eglcapture no
sudo systemctl restart display-manager

You can always log off and log in again, or reboot.

Perhaps not related, but I faced this strange issue just after that

cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.snapd-desktop-integration
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Failed to do gtk init. Waiting for a new session with desktop capabilities.
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Checking session /org/freedesktop/login1/session/_39...
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Is a desktop session! Forcing a reload.
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Checking session /org/freedesktop/login1/session/c2...
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Is a desktop session! Forcing a reload.
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Checking session /org/freedesktop/login1/session/_35...
Jan 24 19:10:51 rpi snapd-desktop-i[13414]: Loop exited. Forcing reload.

On my case, I started receiving some strange errors, which might not be related to this simple line, but in any case, after doing that I entered on some sort of error after error and the display didn’t want to start working again, so I needed a bit more dramatic:

sudo apt install --reinstall ubuntu-desktop

After doing that, and a reboot, all is fine, but most important, CPU consumption is now super relaxed again, and the temperatures are much better:

One of those blog entries that I truly hope it can help somebody on the same situation than me, with similar hardware and software.

Thanks for reading it!

Filed Under: linux Tagged With: nomachine, nomachine cpu, nomachine raspberry pi, nomachine TR01W11263, raspberry pi temperature

Reader Interactions

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

January 2025
M T W T F S S
 12345
6789101112
13141516171819
20212223242526
2728293031  
« Sep   Feb »

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz