> > A workaround is to disable SELinux (at least, it worked for me). > > Hmmm i have selinux disabled already, so that doesn't look like a > workaround for me :-) Strange... did you boot with "selinux=0" kernel boot parameter appended to the kernel command line?