1655
Peasants... (thelemmy.club)
submitted 7 months ago by to c/linuxmemes@lemmy.world
167 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 44 points 7 months ago (24 children)

Can confirm, I'm using arch btw and every three pacman -Syu 's I run into issues that are new to me

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 24 child comments
    •
  • [–] 45 points 7 months ago (10 children)

    One day I will figure out what other Arch users do and why my installation had not a single issue in the 3 years it has been running so far.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 9 points 7 months ago* (last edited 7 months ago) (1 child)

    Jup. I think I've had some 3 actual issues the past 2 years on EndeavourOS. But the Endeavour team did a good job of warning me on Discord/RSS or at least provide tutorials and explanations afterwards.

    One of the issues was in regard to Grub (fixed by Timeshift rollback and a one-liner), one was in regard to some rogue Nvidia bug crashing the login window (fixed by Timeshift rollback and waiting a few days before updating again), and one was Nvidia removing support for GTX1000 cards and older (Nvidia, WHYYYYYYYY?!).

    For reference, I had what felt like similar annoying bugs (and much worse) on Windows 10 about every month, but without any useful support from Microsoft. :(

    EDIT: speaking of the devil. A fourth issue just popped up.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 7 months ago

    and one was Nvidia removing support for GTX1000 cards and older (Nvidia, WHYYYYYYYY?!).

    Yeah this one REALLY sucked on my laptop still running a 960M. But hey, after the fix (which I think was just locking the driver package?) I just don't gotta worry anymore, so that's cool.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 7 months ago (4 children)

    Usually it's graphics drivers going boom on update.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 7 months ago (3 children)

    Yeah but that was communicated in Archnews: https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-kernel-modules/

    Sure the Arch or package maintainers could provide migration scripts for stuff like that (there probably are rolling distros who do that?) or when they split packages but usually you are fine if you read the announcements and act accordingly.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 7 months ago (2 children)

    The question was how they make the arch go boom by running pacman -Syyu and I gave the most probable reason. Thanks for hitting me with RTFM

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 7 months ago (1 child)

    Sorry that wasn't meant like that, I was just pointing out that that was at least communicated in Archnews which not everything is, for example the firewalld package split you have to catch in the package update warnings which is easy to miss.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    Yeah there's a lot of things you can do, but I bet most people just hit yes and go about their day, which is how they break their system. I've done it at least once (come back from vacation and pacman hits you with 300+ new packages), but also have broken arch by trying to install stuff by following old deprecated guides. It's not hard to break, but it's also very achievable to have a problem free time.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 15 points 7 months ago (7 children)

    Heh, that's on you, bazzite here (was arch for a few years 4+ish years ago) can't remember the last time an update was problematic (oh, wait, 42->43 broke a distrobox, but I do that myself all the time, it's what they're for).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 11 points 7 months ago (3 children)

    you know what distro I would choose if I were prone to tinkering at the expense of the system's month-to-month stability?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 7 months ago (2 children)

    On regular Fedora 42->43 broke (or forgot to change?) a few SE Linux rules for me, so that I got constant notifications about violations. Otherwise it's been rock solid so far.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 7 months ago (1 child)

    Yeah, if you dig through journalctl (and you should once in a while) it gives you the commands to fix that stuff if you think it's right. That said, would be nice to not have to do that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 7 months ago

    It's was even easier - KDE showed a notification, I clicked it and got a pop-up telling me about the violation and the commands to fix it of this behavior should be allowed. I could never copy&paste them from there. But yes, checking journalctl every once in a while is a good habit.

    Since it was nothing that really prevented me from using the PC (e.g. virt-manager getting a violation when I shut down a VM), I reported it and waited for a bit if they'd resolve this and then just ran the commands after a two days without fix, because I wanted to get rid of the notifications

  • permalink
  • fedilink
  • source
  • parent