• MalReynolds@slrpnk.net
    link
    fedilink
    English
    arrow-up
    15
    ·
    2 days ago

    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).

    • Sonotsugipaa@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      11
      ·
      2 days ago

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

    • Elvith Ma'for@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      2 days ago

      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.

      • MalReynolds@slrpnk.net
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 days ago

        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.

        • Elvith Ma'for@feddit.org
          link
          fedilink
          arrow-up
          1
          ·
          1 day 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