Last month I have experienced the first major kernel bug in two decades, and all I had to do was reboot into the previous system update. Pretty painless.
I'm personally partial to Arch Linux, haven't had an issue with upgrades since I moved to it in ~2017, which was the last year I let Ubuntu's dist-upgrade break my work computer.
IIRC there have been a couple, but they've not affected the packages I was using, or I hadn't updated before the issues were spotted and resolved. The last half of that point is important: most Linux distros can be trusted to be left alone for 24 hours without coming back to find they've rebooted themselves, potentially losing work (or if not work, at least context so getting back to work takes longer than it should), without permission. Forcing updates and reboots might be acceptable when they cover a serious remote attack exposure bug, but Windows will reboot itself without permission even for relatively minor updates, and the fact it needs to reboot for so many minor things, where under Linux the updates might just need to restart a daemon or two rather than the whole OS, is irritating. Yes, there are ways to block Windows doing that, but you shouldn't have to fight your OS like that.
1) https://web.archive.org/web/20040730204123/http://pack.sunsi...
All my personal computers using intel and amd graphic cards have been faultless using same distro for the last decade.