On Thu, 2008-04-10 at 17:52 -0700, Antonio Olivares wrote: > Do not know what is actually going on! :( It's an selinux policy bug. New installs with that policy (or maybe systems upgraded to that bad policy) will have this problem. Upgrading to later policy doesn't help. I'm going to work with Dan Walsh to create a recovery process for people stuck like this. Until then, set yourself up for permissive mode and you can continue to work. -- Jesse Keating Fedora -- All my bits are free, are yours?
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
