# Are new Plasma bugs triggered by bad usage?

**URL:** <https://forum.endeavouros.com/t/are-new-plasma-bugs-triggered-by-bad-usage/37859>\
**Category:** Plasma\
**Created:** [February 27, 2023, 6:35pm UTC](https://forum.endeavouros.com/t/are-new-plasma-bugs-triggered-by-bad-usage/37859 "2023-02-27T18:35:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![petsam](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/petsam/32/41308_2.png) [@petsam](https://forum.endeavouros.com/u/petsam)\
**Post date:** [February 27, 2023, 7:04pm UTC](https://forum.endeavouros.com/t/are-new-plasma-bugs-triggered-by-bad-usage/37859/4 "2023-02-27T19:04:28Z")

</div>

> [@Eoef](#):
>
> I don’t know if this bug is random or has something to do with the user.

A well known issue with new Plasma versions is that the user often needs to clean cache and/or reset/delete local configuration (kde related) files.

> [@No program opens](https://forum.endeavouros.com/t/no-program-opens/37009/8):
>
> With some plasma/kde developed package updates, several configuration procedures, settings, and/or values change in a way that is not backwards compatible. This often produces such problems in Plasma/KDE sessions, because, while the new packages are installed on the system (system folders/files), the already existing configurations (folders, files) in the users’ folders are not automatically updated. Then, when you login after an update (and reboot), the local files do not include the correct s…

Nevertheless, I have the feeling that this time (5.27), things are worse. We can only hope KDE devs improve this some time (before the end of the world 🤣 ).

---

_[View the full topic](https://forum.endeavouros.com/t/are-new-plasma-bugs-triggered-by-bad-usage/37859)._
