No problem.
When resetting the cache folder is not fixing the problem, you can try to create a new Login. But i guess, just one step at his time… otherwise you can’t be sure, where exactly the issue is coming from.
Btw. Rename a folder should be recommend for caching, you can delete it later anyways.
Besides creating a second login, which probably is the worst option because its resetting all configuration’s (do it only for testing). It’s a huge time sink and probably the most people would prefer a full reinstall since at this point.
I think the most people would prefer smaller steps to fix a error.
Its also recommend to create a Timeshift snapshot before you messing around with your system.
-
Disable widget’s if you have some.
-
Resetting KDE Desktop Layouts to default.
-
You may want to remove old orphan’s from KDE5 with:
sudo pacman -Ru kf5 -
If you have AUR enabled, its worth it to check orphan’s and remove them… specially under Foreign and look for AUR inside which you didn’t had installed manually.
-
Merging .pacnew files with
pacdiff -sand Meld.
I think you both have the same problem, since he is also working with vs code
and experience Desktop crashes: