https://bugs.kde.org/show_bug.cgi?id=460971
--- Comment #10 from kdebuggy <3809940...@gmail.com> --- An UPDATE AND RESOLUTION for this bug: After encountering other bugs too (flickering, Plasma shell dying in a responsive state) I started to suspect that my Plasma configuration which I was keeping for a long time might be the culprit. After searching how to do it, I basically resetted my home folder to a new installation default state. I did this by renaming .kde / .config / .cache directories from a live kubuntu usb to force the system to create clean ones. (I later moved the old config files/directories to the new one except kde/plasma related ones of course) I can say that all my problems are solved (testing for 2 days so far) and KDE is working perfectly with the compositor turned on. SUMMARY: Probably 5.26.1 update didn't cause a direct problem by itself but triggered some instability caused by some very old config option/file interaction. META COMMENT: After this experience I tought about how many KDE bugs people talking about can be resolved by this action. Maybe it is a good idea to add some feature to reset KDE into fresh installation state like Firefox is doing with its "Refresh Firefox" feature. Currently I had to search the net to determine the configuration files/folders and I compared them with a fresh test user I created for this purpose. Also I had to do this from a live linux usb. This is beyond an average user's skill set and an option to quickly return the plasma to a known state might be very helpful when dealing with mysterious bugs. This is a preliminary comment and I will update after some more usage to be sure. I encourage other users suffering from this bug to try the cleaning method and confirm my results. -- You are receiving this mail because: You are watching all bug changes.
