# Plasmashell –no-respawn taking too much CPU

**URL:** <https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002>\
**Category:** Help\
**Created:** [April 13, 2024, 9:40am UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002 "2024-04-13T09:40:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ExistingProgrammer](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/existingprogrammer/32/11644_2.png) [@ExistingProgrammer](https://discuss.kde.org/u/ExistingProgrammer)\
**Post date:** [April 13, 2024, 9:40am UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/1 "2024-04-13T09:40:43Z")

</div>

![image](https://discuss-cdn.kde.org/uploads/default/original/2X/9/9b58465cdf06ef38ed9fac66383a493ae1279f26.png)  
Restarting plasmashell with  
`killall plasmashell; systemctl --user restart plasma-plasmashell`  
fixes it, but it reappears on reboot or if I open the application launcher on the taskbar.

**Tested in a new user. Issue still persists.**

`systemctl --user status plasma-plasmashell`

 ![image](https://discuss-cdn.kde.org/uploads/default/original/2X/1/18ba0b64895d979a4002fc83ee4cac5f1a08c1f7.png)

Kernel: 6.8.4-zen1-1-zen  
Theme: [Plasma], Catppuccin-Mocha-Standard-Lavender-Dark [GTK2/3]  
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3]  
CPU: Intel i3-8100 (4) @ 3.600GHz  
GPU: NVIDIA GeForce GTX 1050 Ti

---

<div class="post-metadata">

**Author:** ![rockandstone](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/r/7cd45c/32.png) [@rockandstone](https://discuss.kde.org/u/rockandstone)\
**Post date:** [April 13, 2024, 2:41pm UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/2 "2024-04-13T14:41:23Z")

</div>

~~I can’t confirm if it is using too much CPU right now~~ _/edit:_ it doesn’t , but I wouldn’t kill plasma like that as it doesn’t terminate things “gracefully”, (nor do you give it much time with `;` to begin with). If I’d need to reload configs and restart I’d use

```auto
systemctl --user daemon-reload && systemctl restart --user plasma-plasmashell.service

```

---

<div class="post-metadata">

**Author:** ![ExistingProgrammer](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/existingprogrammer/32/11644_2.png) [@ExistingProgrammer](https://discuss.kde.org/u/ExistingProgrammer)\
**Post date:** [April 14, 2024, 5:37am UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/3 "2024-04-14T05:37:05Z")

</div>

Thank you! This is more consistent to restart plasmashell then the command I was using. But it doesn’t fix the underlying problem. The issue reappears on opening application launcher.  
As a workaround, I will hotkey this command to a shortcut to quickly restart plasma.

---

<div class="post-metadata">

**Author:** ![ExistingProgrammer](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/existingprogrammer/32/11644_2.png) [@ExistingProgrammer](https://discuss.kde.org/u/ExistingProgrammer)\
**Post date:** [April 14, 2024, 6:47am UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/4 "2024-04-14T06:47:02Z")

</div>

kwin\_wayland seems to be related to plasmashell --no-respawn in that it also stops using so much cpu when I restart plasmashell with this command.

---

<div class="post-metadata">

**Author:** ![ExistingProgrammer](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/existingprogrammer/32/11644_2.png) [@ExistingProgrammer](https://discuss.kde.org/u/ExistingProgrammer)\
**Post date:** [April 16, 2024, 1:53am UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/5 "2024-04-16T01:53:12Z")

</div>

> **[How reset all KDE settings?](https://forum.manjaro.org/t/how-reset-all-kde-settings/21518/3)**
>
> I used solution from \[here was a link\] Logout from KDE and run: cd ~/ rm -rf .kde rm -rf .cache/plasmashell\* rm -rf .cache/org.kde.dirmodel-qml.kcache rm -rf .cache/kioexec/ .cache/krunner/ .cache/ksycoca5\* rm -rf...

Doing this helped for some reason even after creating new user didn’t.

---

<div class="post-metadata">

**Author:** ![usr\_40476](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/usr_40476/32/4599_2.png) [@usr\_40476](https://discuss.kde.org/u/usr_40476)\
**Post date:** [April 16, 2024, 7:10pm UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/6 "2024-04-16T19:10:00Z")

</div>

I am also having this problem, how do i fix it without completely resetting?

> **[Plasmashell has been using extra system resources](https://forums.opensuse.org/t/plasmashell-has-been-using-extra-system-resources/174270)**
>
> A few updates ago I noticed that plasmashell has regularly been using about 10-18% CPU and some extra RAM on a regular basis this never happened, is something wrong?

> [@Plasmashell using extra resources](https://discuss.kde.org/t/plasmashell-using-extra-resources/14153):
>
> A few updates ago I noticed that plasmashell has regularly been using about 10-18% CPU and some extra RAM on a regular basis this never happened, is something wrong?

> [@Plasmashell –no-respawn taking too much CPU](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/6):
>
> I am also having this problem, how do i fix it without completely resetting? [https://discuss.kde.org/t/plasmashell-using-extra-resources/14153](https://discuss.kde.org/t/plasmashell-using-extra-resources/14153)[https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/6](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/6)

---

<div class="post-metadata">

**Author:** ![Prem](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/p/8797f3/32.png) [@Prem](https://discuss.kde.org/u/Prem)\
**Post date:** [September 1, 2024, 12:13pm UTC](https://discuss.kde.org/t/plasmashell-no-respawn-taking-too-much-cpu/14002/7 "2024-09-01T12:13:22Z")

</div>

> [@rockandstone](#):
>
> `plasma-plasmashell.service`

In my case, the `PlasmaShell` process is jumping between 10% and 30% CPU usage in htop. But I’ve discovered this only happens when certain applications are running, namely `Chromium` or `Brave browser`. Both are Electron apps, but other Electron apps, such as `Codium` and `Teams`, are not causing this issue.

And restarting `plasma-plasmashell.service` didn’t help it my case…
