Description of problem: System-config-securitylevel fails to apply changes to config files. Run from a terminal it generates a python traceback. Version-Release number of selected component (if applicable): system-config-securitylevel-1.6.16-1 How reproducible: Always (on our test system at least) Steps to Reproduce: 1. Launch system-config-securitylevel 2. Press OK 3. Actual results: In the graphical interface nothing happens (the window doesn't close). When launched from a terminal a python traceback is generated. Expected results: Security settings are correctly updated. Additional info:
Created attachment 126619 [details] Python traceback generated when the OK button is pressed.
What are the results of rpm -qa selinux\* ?
# rpm -qa selinux\* [nothing! Which seems odd...] # rpm -qa | grep selinux libselinux-1.30-1.fc5 libselinux-devel-1.30-1.fc5 libselinux-python-1.30-1.fc5 This is a machine which was upgraded from FC4, and on which I believe selinux had previously been disabled. Looking at /etc/sysconfig/selinux I saw that it was now set to enforcing with the file having the date stamp of the upgrade to FC5. I then did yum install selinux-policy-targetted, and system-config-securitylevel now works. Not sure how this happened, but could it be that anaconda overwrote the old config file during the upgrade and left selinux in an odd state?
Looks like there's two bugs here - first, s-c-securitylevel shouldn't be exploding in the case of there being no selinux stuff installed. Second, it looks like anaconda's driving over your selinux settings on upgrade. Could you please file a bug against anaconda for that aspect of it?
*** Bug 187701 has been marked as a duplicate of this bug. ***