9:05 PM For me, recreating the profile from scratch was the solution, steps taken:
I open a terminal Ctrl-Alt-F2 with my current user (If my home/user is “mre”):
$ cd /home/ # sudo mv ./mre ./mre.bak # mkdir ./mre # chown mre:mre ./mre
reboot
After reboot the PC, copy carefully all the folders and settings from the previous backup home on the new one. Things like:
~/.kodi
~/.mame
~/.mozilla
~/.remmina
~/.ssh
~/.telegram
~/.thunderbird
… etc.
And much more carefully copy the content (of what you can recognize) of the following:
~/.cache
~/.local
~/.share
Check during each copy that the disgusting bug is not activated.
If the bug is reactivated, then you can probably determine the cause of the problem. From what I see, the problem seems to be related to Bauh, flatpak or appimage. Since I didn’t copy anything from your folders wherever I saw references to these.
Note: not everything will work correctly; for example: remmina is asking me for the passwords to connect… if I haven’t forgotten them, everything is solved (for me).
This is not easy, it is not fast, but after lasting +1 month with this ugly glitch, investing 1 or 2 hours is worth it.
Finally reboot to see the bug gone for now, until the KDE developers trip us up .
And if any of the KDE developers read this (I don’t think so), hopefully it will serve as a background for what they might do during each major plasma and component upgrade: reset the KDE and component configuration.
I PREFER that the plasma/desktop configuration is reseted to suffer this bug that prevents the use of KDE.
This is my solution, now I need to perform it on the PC I use at work, hopefully I will only lose the decorations I installed without losing a day or 2 hours of work.
I hope it will be useful to those like me who don’t want to leave KDE and switch to the awful gnome versions.
Regards,