• @rtxn@lemmy.worldM
      link
      fedilink
      04 months ago

      2-3 years ago, an update to GRUB completely fucked the bootloader on Arch systems. I remember it well because it was the only time I was thankful for choosing Manjaro (which receives updates on a delayed schedule).

      • @Speiser0@feddit.org
        link
        fedilink
        04 months ago

        Upgrading on arch involves looking at the arch news. And IIRC, there was also a warning for some time when upgrading grub. So, assuming people who use arch, btw, use it properly, I don’t see the issue.

    • @HatFullOfSky@lemmy.world
      link
      fedilink
      04 months ago

      I’ve had two instances in the past year on Purple Arch (Endeavor) where a kernel update “broke” my system. In both cases, the system still booted fine though, so not all definitions of "broken"may apply.

      The first time there was a bug with the kernel drivers for my wireless card which caused a component of Network Manager to lag out the entire UI to the point it was basically unresponsive trying to find a connection, but never did.

      The second time, it was a bug with the Vulkan drivers that caused all my games to crash within 60 seconds of starting up. Games are the main thing I use my PC for, so my system was effectively “broken”, even though everything else was fine.

      I am of course not discrediting your fortune - I merely wanted to share

      • @Petter1@lemm.ee
        link
        fedilink
        04 months ago

        Yea, that is not your system broken, but just an package update that was faulty, and probably fixed with an update a few hours later, isn’t it?

        And you were able to role back such packages with yay/pacman, I suppose?