plasmashell high cpu usage

im getting really high cpu usage on plasma and its making my whole system crawl
Operating System: Bazzite 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-ba01.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: AMD Radeon RX 7900 GRE
Manufacturer: ASRock
Product Name: B650M Pro RS WiFi
Operating System: Bazzite 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-ba01.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: AMD Radeon RX 7900 GRE
Manufacturer: ASRock
Product Name: B650M Pro RS WiFi
ignore the winboat windows vm it just started so thats why its using so much cpu it evntually calms down but the plasma shell cpu usage doesnt
No description
Solution:
Turns out it was decky I disabled the decky service and my CPU usage went down dramatically as well as ram. Strangely plasma shell CPU usage went down to about 10% after stopping decky too So what I resolved to do is disable decky when I'm in desktop mode and renable it when in game mode ...
Jump to solution
3 Replies
zany130
zany130OP2w ago
Bazzite buddy too..... I also noticed high ram usage in several other deck plug-ins strange thing is this is only in desktop mode
No description
Solution
zany130
zany1302w ago
Turns out it was decky I disabled the decky service and my CPU usage went down dramatically as well as ram. Strangely plasma shell CPU usage went down to about 10% after stopping decky too So what I resolved to do is disable decky when I'm in desktop mode and renable it when in game mode Lucky plasma has some scripting options that allows automating this https://docs.kde.org/stable5/en/plasma-workspace/kcontrol/autostart/index.html You can run stuff before kde starts and then you can run another script when kde shuts down aka switch to game mode Bonus this solves other annoyances with decky in desktop mode like audio loader still playing ambient music when steam is running in desktop mode
zany130
zany130OP2w ago
apperently you can also use a polkit rule like this one
sudo cat /etc/polkit-1/rules.d/90-plugin-loader.rules
polkit.addRule(function (action, subject) {
// Allow only start/stop for *this* unit, for members of "wheel"
if (action.id === "org.freedesktop.systemd1.manage-units" &&
(action.lookup("verb") === "start" || action.lookup("verb") === "stop") &&
action.lookup("unit") === "plugin_loader.service" &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
sudo cat /etc/polkit-1/rules.d/90-plugin-loader.rules
polkit.addRule(function (action, subject) {
// Allow only start/stop for *this* unit, for members of "wheel"
if (action.id === "org.freedesktop.systemd1.manage-units" &&
(action.lookup("verb") === "start" || action.lookup("verb") === "stop") &&
action.lookup("unit") === "plugin_loader.service" &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
this allows any member of the wheel group to manage the plugin_loader.service without root just tried it and it does let me run systemctl start plugin_loader.service and systemctl stop plugin_loader.service without entering a password just need to test if plasma runs the sthe scripts correctly
/usr/bin/cat .config/plasma-workspace/env/disableDecky.sh
#!/usr/bin/env bash
systemctl stop plugin_loader.service
/usr/bin/cat .config/plasma-workspace/env/disableDecky.sh
#!/usr/bin/env bash
systemctl stop plugin_loader.service
and
/usr/bin/cat .config/plasma-workspace/shutdown/enableDecky.sh
#!/usr/bin/env bash
systemctl start plugin_loader.service
/usr/bin/cat .config/plasma-workspace/shutdown/enableDecky.sh
#!/usr/bin/env bash
systemctl start plugin_loader.service

Did you find this page helpful?