Kernel Manager terminology is misleading (“SUSPENDED” vs. “Not Installed”)

Hi team,

I’d like to report a small but important UX issue in the Kernel Manager (the module launched from Update Manager via View → Linux Kernels). The Kernel Manager labels the currently running kernel as ACTIVE, which is clear and correct. However, all other kernels in the list are labeled SUSPENDED, even when those kernels are not installed on the system and do not exist in /boot.

In most Linux contexts (systemd, power management, PipeWire, kernel modules), “suspended” means:
installed
present
loaded but idle

But in the Kernel Manager, “SUSPENDED” is used to mean:
not installed
not present on disk
simply available in the repository

This can easily lead users to believe they have many kernels installed when they do not.

Suggested improvements:
Replace “SUSPENDED” with a clearer term such as:
“Not installed”
“Available”
“Repository version”

Visually separate:
Installed kernels
Available kernels

This would make the Kernel Manager’s behavior match Linux conventions and reduce confusion about what is actually on the system.

Thanks for considering this — the tool is very useful, and this small change would make it even clearer.

Start at the Kernel Manager entry point launched from Update Manager via View → Linux Kernels. Inspect how the kernel list labels the active kernel and other entries, and how installed kernels are distinguished from repository versions. Done means the terminology no longer implies that uninstalled kernels are suspended and the installed-versus-available presentation is clear.