This week, I needed to declare the KDE experiment a failure. While there are many ways in which I prefer it to GNOME, there are just as many annoying quirks that I did not manage to tame or get used to. Since Fedora 33 is about to ship, Fedora 31 is about to become unsupported anyway, so it seemed like a good time to upgrade.

Out of laziness, I decided to do a clean install. There are enough differences (display manager, etc.) between the KDE spin and the standard workstation spin of Fedora that I didn’t want to end up with some weird combination of the two. I know enough patience with the package manager can straighten those out, but reinstalling isn’t hard and I have good backups.

It’s a good thing I have good backups, because I promptly managed to nuke my /home partition when I set about doing a clean install.

Other than that, the installation went smoothly, and long-held Linux installation habits led to the user ids for the users I always create when I install being identical, so restoring the backup of /home was quick and painless.

Naturally, just like last time, the boot SSD got really slow, as if it were filled to capacity. Under Fedora 32, though, there was no need to boot to rescue. fstrim -a appears to have just worked.

I’d like to understand why the installer does not issue that command as part of the setup process.