hmm... this dbus error is a bugger.. spent yesterday and most of today on this. (and I know I said I was going to goto a kernel bug). Anyways: seems after doing a fresh install then installing the selinux apps/libs the system has not done an initial relabel, upon reboot gdm will restart/flicker 5 times before erroring out, then drop you to a general login. If I chmod 644 /etc/selinux/config this goes away. (my guess is libselinux didn't have the permissions to read the config defaulting to "targeted"). but as soon as I relabel the filesystem the dbus error will appear(but not the screen flickering 5 times). when this happens I: vim /etc/selinux/refpolicy-standard/booleans and change init_upstart to true. then I can bootup. why is init_upstart needed in order for this to work, when this system uses sysvinit? positive side is this thing boots up without the need for the policy to be named targeted. Justin P. mattock -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
