Just an update i fixed this and i can boot properly. The only problems i got so far are that loginctl doesnt show any sessions and polkit doesn't work for either of my users(thats possibly a consequence of systemd-logind not being able to identify the logged in users). I got this: systemd-logind[355]: Assertion 's->user->slice' failed at ../src/login/logind-session.c:496, function session_start_scope(). Aborting. On 05/28/2015 03:11 PM, George Karakougioumtzis wrote: > Hi. I am hit by the same exact bug as described here > https://bugzilla.redhat.com/show_bug.cgi?id=1099299 > > but this is an already upgraded f21 machine. The problem is i cant > enforce selinux i have the boot loop described in the bug. > I have upgraded initscripts and systemd as per the bug. I reinstalled > selinux-policy-targeted just in case. > All i get is a failure of systemd-journlad-dev-log.socket and both > systemd-journald.service and systemd-udevd.service. Any hints? I already > tried to autorelabel but that didnt fix it. -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux
