EDIT:
Preface: If I have a system with issues and buggy behavior, how can I reset KDE to its initial state? The usual defaults from System Settings won’t apply since there’s something borked.
I don’t want to nuke my whole ~/.config because I have other, valuable files in there.
I sam that the naming of the files is not systematic, and they are in subfolders and also the root of the .config folder.
Quite tedious to find them all.
Create backup 2 files first !!!
Then try:
rm ~/.config/plasmashellrc
rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Then logout and login. Or just better - reboot.
user623 showed a much easier scheme than I will describe, but KDE keeps user data in other places as well. If his method wasn’t adequate, here’s the more complete method I recently used on my own “main” UserID under Tumbleweed.
~/.config does contain other plasma related directories, but so does ~./local/share
To perform a really safe backup and restore, if the /home partition has enough space, do this instead:
As preparation (while running as USER), first export passwords which applications (including many browsers, e.g. chromium and brave) might be saving relative to your KDE “Wallet”. (I found it too hard, if not impossible, to effectively “import” the secrets from an older wallet to let me Brave browser use my existing passwords collection by “merging” wallets as root.) I exported to a CSV file, and imported later, from within Brave, before deleting the CSV export file.
That’s what I did, although a more complex idea might also work: after mv of the old /home/USER to /home/USER_backup and creation of the new, empty /home/USER directory (and correcting ownership to USER, rather than “root”), maybe you could just rsync (archive) the old wallet directories from the /home/USER_backup/.local.share wallet data location into ./local/share of the otherwise empty new /home/USER directory. But I’m not sure that KDE “first login” stuff is smart enough to build everything nearly everything else “new” while finding an existing kwallet and leaving it active – so I saved stuff from within the applications themselves. Here are your steps:
USER now has an empty /home directory. It will become filled with new user default settings upon first login. But you might want to rysnc those wallet directories from ~/.local/share before logging in, if you did not save “wallet” related data to an importable or human-readable file first. (Again, that might not prevent KDE from building a new user wallet anyway, at first login. I don’t know whether that could work.)
In any case, however, You still have that backup of the “old” /home, from which you can ‘mv’, or ‘cp’, or ‘rsync’ all of your existing data structures without the hassles of changing ownership or groups. I suggest ‘mv’, or ‘rsync’ with complete archive options. rather than ‘cp’, because Selinux stuff can get lost by ‘cp’ with slightly incorrect options.
‘mv’ actually renames the files and directories into the new place without new disk space, but your old and ‘slightly messed up’ backup directory becomes less complete. If you have lots of spare disk space (as I did), rsync leaves the old backup intact – and you could even log in again, with your old stuff and old config intact, by renaming the ‘newer’ versus ‘backup’ directories as ‘root’ a second time.
Settings > Colors & Themes > Global Theme
Set to Breeze or Breeze Dark