Description of problem: When I delete an alert in SELinux Alert Browser, it reappears after reboot. Version-Release number of selected component (if applicable): setroubleshoot-3.3.15-1.fc27.x86_64 How reproducible: Every time Steps to Reproduce: 1. sudo mv /etc/resolv.conf /etc/resolv.conf.saved 2. sudo cp /etc/resolv.conf.saved /etc/resolv.conf 3. Reboot and login 4. Open SELinux Alert Browser 5. Select "troubleshoot" for every warning and run the suggested solution (restorecon) 6. Delete every warning 7. Reboot and login 8. Open SELinux Alert Browser Actual results: The warnings are still there. Expected results: There should be no warnings. Additional info:
Doesn't require a reboot. Just start a new seapplet instance.
@Petr, this is a regression after the switch to GTK3.
I have this problem too :( If someone need some logs etc. Pls write down which you need.
I've added save interface to rpc and it's called every time an alert is deleted in browser. Could you please try the following build from my plautrba/setroubleshoot COPR repo? https://copr.fedorainfracloud.org/coprs/plautrba/setroubleshoot/build/716483/ or use the following commands: # dnf copr enable plautrba/setroubleshoot # dnf update setroubleshoot
Created attachment 1397097 [details] Screenshot Don't works
*work
Sry for the spam.... Doesn't work
I've tried setroubleshoot-3.3.16-0.fc27.30.x86_64 and it worked for me. Thanks, Petr.
Updating to setroubleshoot-3.3.16-0.2.fc27.x86_64 from the copr repo gives me mixed results. When I delete alerts in the sealert GUI, sometimes they reappear the next time I open sealert. However, other times they stay deleted, even after a system reboot.
setroubleshoot-3.3.17-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c6be5e935b
setroubleshoot-3.3.17-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c6be5e935b
The latest update that was pushed to the copr repo seems to have done the trick for me. I'll try the version that's on the testing repo too, unless it's the same version as what's on copr.
It's basically the same code but with a higher release. setroubleshoot-3.3.17-1.fc27 will be soon in stable anyway so you can wait for that.
setroubleshoot-3.3.17-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.