I accidentally pulled in a bad test update for fwupd and started getting systemd complaints that it couldn't start it, which led me down the "Google the error message" rabbit hole.

Apparently, something caused this problem in Fedora 31 late last year and it involved systemd auto-respawning a "tpm" service, and then having the service die if the person didn't have a TPM, or turned it off, and going into a loop of having it die and bringing it back. So I tried removing the packages that had the TPM crap in them because I don't have a TPM. Nope.

What I did stumble into is that I pulled in fwupd 1.3.7 as a test update, and something about it changed in a way that selinux didn't like, and so selinux was blocking it from accessing a path that it needed. So, yeah, it's a test update, but apparently it went down that chute without _anyone_ noticing that selinux breaks it and that, in turn, breaks GNOME Software checking for updates.

This is starting to feel awfully like Windows 10.

Edit: And now fwupd works, but GNOME software says it can't download the repo metadata because of course it can't. (Something about the checksum mismatching what it was expecting.)

To quote Dr. Evil, "Well, shit.".

Time for a project to find another Linux distribution that at least tries dealing with the shit hitting the fan from Red Hat.

I shall call it........The Alan Parsons Project.

MUAHAAHAHHAHAHAHAHAAAAA!!!!

Then again, I disabled the Fedora Modular repos it was bitching about because the only possible use for these seems to be if you're a developer and need a different version of a database or runtime or something and it's really....I don't even think these should be enabled by default, personally, because it just slows down DNF anyway.