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).
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.
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.
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
Just nuked my CachyOS install with a routine update and switched to Bazzite after repairing it in chroot failed. I enjoyed the entire process, even the failures.
Can confirm, I’m using arch btw and every three
pacman -Syu's I run into issues that are new to meHeh, 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).
you know what distro I would choose if I were prone to tinkering at the expense of the system’s month-to-month stability?
lmao :) Have fun.
It’s been 9 years since I set my system up, so…
Please do.
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.
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.
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
You get issues every fifteen minutes? Damn.
I’m on arch now (BTW) and I’m eyeballing fedora atomic sway.
Just nuked my CachyOS install with a routine update and switched to Bazzite after repairing it in chroot failed. I enjoyed the entire process, even the failures.
https://github.com/bradford-smith94/informant
This will help big time. 😏
nah, I visit archlinux.org before updating but most of the pain is self-inflicted