not OP, and not Arch, but Manjaro (so you can take it with a grain of salt), reporting from memory so details might be incorrect. * after "BootHole" GRUB vulne

not OP, and not Arch, but Manjaro (so you can take it with a grain of salt), reporting from memory so details might be incorrect. * after "BootHole" GRUB vulnerability, I've read that upgrade requires re-installation of the bootloader. And just in case, did run `sudo grub-install …`. After reboot, system didn't boot. Had to use installation USB to restore. * More recently, during routine upgrade pamac (Manjaro's pacman alternative) GUI showed me some "transaction can't be completed" error message. Shuddered it away - few days later pamac wasn't starting at all. Starting it from terminal showed error message about some missing *.so file. Googling showed that this is a required file for pacman (Arch package manager) to function. Typing `pacman` in terminal showed "command not found" error message. Restored the missing *.so file from snapper snapshot (thanks btrfs!), after that pamac started fine and happily upgraded my system. I'm not sure what happened in second case and why pamac left system in broken state (looks like it wanted to upgrade pacman by first removing old files and then putting new files in place, but aborted in the middle), but first one might be quite distro-independent. Also, reading through recent Arch news, I believe this could bite someone: https://archlinux.org/news/sshd-needs-restarting-after-upgrading-to-openssh-82p1/ https://archlinux.org/news/sshd-needs-restarting-after-upgra... > After upgrading to openssh-8.2p1, the existing SSH daemon will be unable to accept new connections. When upgrading remote hosts, please make sure to restart the SSH daemon right after running pacman -Syu. If you are upgrading to openssh-8.2p1-3 or higher, this restart will happen automatically.