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