Description of problem: May 02 16:09:53 chainsaw.msnomer.com systemd[1]: dbus-:1.4-org.fedoraproject.SetroubleshootPrivileged: Failed with result 'signal'. May 02 16:09:53 chainsaw.msnomer.com systemd[1]: dbus-:1.4-org.fedoraproject.Setroubleshootd: Main process exited, code=killed, status=14/ALRM May 02 16:09:53 chainsaw.msnomer.com systemd[1]: dbus-:1.4-org.fedoraproject.Setroubleshootd: Failed with result 'signal'. Version-Release number of selected component (if applicable): 3.3.26-1.fc34 How reproducible: Very Steps to Reproduce: 1. Boot to Fedora 34 2. 3. Actual results: Alerts each time Setroubleshoot needs to run Expected results: No alerts each time Setroubleshoot needs to run Additional info: Upgraded from Fedora 33 to 34. Since there are a few problems with SELinux that need to be ironed out, Setroubleshoot is triggered quite frequently and, each time is is, a new service failed message appears in the journal as well as in the Services page in Cockpit.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug in setroubleshoot does still exist in Fedora 36 and is always reproducible. May 13 11:06:31 example.org systemd[1]: dbus-:1.3-org.fedoraproject.Setroubleshootd: Main process exited, code=killed, status=14/ALRM In my case the crash is, for example, triggered by https://bugzilla.redhat.com/show_bug.cgi?id=1293744, which was also never fixed and nevertheless closed. Can somebody with the required permissions please set this bug report's version to '36' so that the bug isn't closed when Fedora 34 reaches its end of life?
It should be fixed in the next release by https://gitlab.com/setroubleshoot/setroubleshoot/-/commit/d98093f251a150cca70fcc55d3e68fe421c84b87
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.