Ask Your Question

Revision history [back]

As noted in the common-bugs page, this bug is resolved with an updated SELinux policy selinux-policy.noarch 0:3.12.1-117.fc20. In order to successfully resolve it, follow the instructions posted there:

setenforce 0
yum clean expire-cache
yum update selinux-policy\*
setenforce 1

Feel free to check out this thread as well on

Additionally, if for some reason your issue is still not resolved, you might have to relabel the file system like so:

# touch /.autorelabel
# reboot

NOTE: this will take some time during the boot-up process to relabel all files according to your updated SELinux policy; so, be patient during that boot-up!