Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #1740936
I am copying this bug because:
Description of problem: When trying to remove a Policy Module with priority other than 400 via GUI, it fails when it cannot find the module with priority 400 to remove.
Version-Release number of selected component (if applicable): '2006'?
How reproducible: Worked every time for me.
Steps to Reproduce:
1. Add policy for something, I used "my-qemusystemx86", priority != 400
2. Open system-config-selinux and go to Policy Module and search for your policy
3. Click remove, it will fail as long as there isn't a priority 400 for it
Actual results: Complains about no priority 400 to remove
Expected results: Removes priority Y Policy Module
Additional info: Seems to just be calling the command "semodule -r NAME" when it should be calling "semodule -x PRIORITY -r NAME"
The scenario will be tested in Xorg session, because the system-config-selinux tool is able to run in that session. The same tool segfaults in Xwayland session.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1779