• Hiro8811@lemmy.world
    link
    fedilink
    arrow-up
    19
    arrow-down
    1
    ·
    18 hours ago

    What? I never had an update break my system on Arch, even with nvidia proprietary drivers.

    • HatFullOfSky@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      15 hours 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
        arrow-up
        1
        ·
        9 hours 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?

    • SaharaMaleikuhm@feddit.org
      link
      fedilink
      arrow-up
      1
      ·
      11 hours ago

      I had issues with Arch all the time. Now is that the fault of my system being dodgy or my lack of skills? Probably. I even have wifi SOMETIMES not work on Mint.

    • rtxn@lemmy.worldM
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      16 hours 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).

      (edit) Found it! https://archlinux.org/news/grub-bootloader-upgrade-and-configuration-incompatibilities/ A breaking change in the GRUB configuration caused systems to become unbootable. Manual intervention was required to regenerate the config files (I think it was supposed to be handled by a pacman hook but can’t be sure).