STEPS TO REPRODUCE 1. run desktop-installer from a sudo inside konsole (ill advised) 2. I think there was a dependency failure about a transcode library, and that freaked the script out, and after attempting to install turbo jpeg for ports instead of pkg ( I realize now that I did not install it from ports, we probably need to add that to the platform options, or someone can move it to other) 3. it started to uninstall stuff, I thought it was just deleting downloaded files, but nope, konsole crashed, and all the other applications crashed too, just left with a plasma shell that could log out. 4. Reinstall KDE5 (pkg install kde5) 5 -- observe 6, move the .dbus .kde and .config folders to another location. 7. login with KDE X11 session, and it is back to a default install. OBSERVED RESULT After reinstalling, all the desktop icons were corrupted, and the list of applications in the launcher were corrupted. EXPECTED RESULT A. Errors instead of vanishing apps... but we can't control everything when root yanks stuff out from under us... B. An uncorrupted version of settings that just work when the applications are reinstalled. C. some sort of detection and re-running of the initial program that scans and catalogs applications and configures toolbars and panels. -- A dialog that says: Corrupt settings detected, restore to system default? and copies the corrupted settings to a spot that could be restored if uncorrupted. D. Human readable settings... I know from in the past, I tried to set up a lab to have KDE configured like a kiosk, and KDE likes to save binary blobs and stuff in the configuration files. SOFTWARE/OS VERSIONS latest from freeBSD13.1 as of Sunday 2/26/2023 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5 KDE Frameworks Version: 5 Qt Version: 5 ADDITIONAL INFORMATION This is actually fairly important for keeping the system reliable. Detecting faults and being able to recover shouldn't be too hard, hopefully not used often, but people like to bork their systems.
Hmm, I don't think there's a KDE bug here. If the system has been installed incorrectly, *nothing* is going to work right. There's no reason for a fresh installation to leave the system in a broken state. If it does, that's an issue with the installer or the way it was run. ;) When you DIY things, it's up to you to ensure correctness for basic stuff like installing the system.