Title says it all. Rebooted, same condition. Plasmashell is completely pegged at 100% CPU. Makes the system almost unusable.
Going to have to do a rollback… I’m not going to update my backup Beelink system, either, until this is fixed.
Title says it all. Rebooted, same condition. Plasmashell is completely pegged at 100% CPU. Makes the system almost unusable.
Going to have to do a rollback… I’m not going to update my backup Beelink system, either, until this is fixed.
Do you login with “Plasma / Wayland” selected?
If yes, try a login with “Plasma / X11” and see how it works.
Nope. I use X11. I asked DeepSeek about this, it suggested plasmashell could be running some reinitialization since it’s a new version. I’m going to reboot again and see if it re-occurs.
Don’t trust AI’s
I took it with a grain of salt, as I always do.
However, on a reboot, it appears that the 100% CPU is just normal plasmashell initialization. It drops off after a couple minutes and the system returns to norma.
So, false alarm, I guess. Probably was doing normal initialization and it took a little longer on first reboot after installing the new version.
Went ahead and did the update on the Beelink machine. Interestingly, it didn’t do it there. System came up as normal.
So…weirdness… Oh, well…
Do you have file indexing turned on???
Good question … the “Baloo” indexer has been notorious for high CPU usage for extended periods of time.
Today, KDE crashed on me. For a long time, Baloo and GDB had been overloading KDE, and the disk often spun up to high speeds. I deleted the .config
, .kde
, and .qt
directories—after a restart, it helped a bit, but plasmashell
was still at 100%, the taskbar was empty, and I had to set everything up again multiple times because KDE kept freezing. After a while, it would freeze again. GNOME runs fine. I scanned the partitions, and they were error-free. Reinstalling again:
bash
KopiujEdytuj
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.loadDefaultLayout
```sudo zypper install plasma-workspace .
I also ran clamdscan. Antiviruses detect Windows i Linux in the project https://wiki.free pascal.org/LAMW
You should not have done that.
balooctl stop
rm -rf ~/.local/share/baloo
balooctl start
Regenerates the baloo database, that is most likely corrupted