Version: 197 (F18) Seems my selinux fs labels got hosed somehow in my F18 VM. As a result, on next reboot, systemd failed to start dbus.service and went completely nuts trying to start it over and over again. All I could do was to forcefully reboot (and start with selinux=0 and forcing a relabel). You can easily "simulate" the problem by using ExecStart=/bin/false in dbus.service. systemd should behave much better in such a case. The least it can do is to stop trying after a while and offer a rescue shell or just continue to boot, since systemd should still be basically functional without a running dbus system bus.
I accidentally fucked up the restart suppression logic. This is fixed in git now (and I think michich backported that to F18), with that in place C-A-d at least should work fine still...
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.