It may have instructions on how to update without borking your system. For example, the February update broke Plymouth, causing systems using it to be unbootable. Sort of. It would actually boot, just to a black screen. On one of the threads someone reported being able to SSH into his PC just fine.

Or the May update bringing Plasma 6 to stable. The recommendation was to reset Plasma to defaults, log out, stop SDDM and update from TTY. I tested doing exact opposite of that in VM, and it still went fine, except for missing icons, but still a good idea just to be safe.

But I had some other problems too.

February update: Booting to black screen. I found threads mentioning the same stuff for this update. Cool. "Remove Plymouth or just don't use splash". I... already disabled splash (and quiet to make boot-up cooler).
Fix: Updating Linux 5.15 LTS to 6.6 LTS. Something changed in 5.15 making it break on my laptop, I guess. I couldn't even get to TTY without nomodeset.
Furthermore, the animations became choppy after resuming from sleep.

May update: Turning on Bluetooth may cause system crash. It would show as "ON", but actually be inactive while shoving already paired devices. This couldn't be reversed. Logging out and back in would lead to only the welcome screen and yakuake showing up. Trying to reboot from both yakuake and plain TTY would stop mid-way. After issuing reboot, the system would be mostly dead, but still kinda running. Linux still responded to magic SysRq.
Fix: Upgrading Linux 6.6 LTS to 6.9.

So, I can deal with it, and it definitely taught me to use Timeshift. Oh, and the brightness buttons sometimes stop working.

[–] balder1993@programming.dev 2 points 5 months ago

That’s the same thing I’d do when o used Arch. Always kept up to date to announcements of something major like a DE upgrading and usually would reset all the settings just in case. It avoided me any problems during the years I ran it.