[systemd-devel] WTF changed after version 208? systemd won't boot again!

[Aaron Lewis]

Hi,

I'm sure what changed in version 209, everything is just fine in 208.

Now I can't boot my system once again. (Downgrade always works)

Here's the problem at boot,

I get a dev-sda1.XX timeout message, that's just weird.
Checked journalctl -xn, nothing helpful, only a few lines says dependency fails

Then I ran systemd-analyze, it says
Failed to start message bus: No socket received.

I did a strace, looks like /run/dbus does not exist, so I created one,
the error persists.

If I run systemctl start dbus the whole system stuck. strace shows it
stuck on msgsend, some 'dbus replace' message, can't recall more

It looks like a dbus problem, what should I do now?
I already have tons of software masked from upgrade, which is all
linked to libsystemd.so, hehe

I'm running Arch Linux, software version:
dbus 1.8.0-1
dbus-glib 0.102-1
dbus-sharp 0.7.0-4
dbus-sharp-glib 0.5.0-4
lib32-libdbus 1.8.0-1
lib32-systemd 212-1
libdbus 1.8.0-1
libdbusmenu-qt 0.9.2-2
libsystemd 212-1
perl-net-dbus 1.0.0-3
python-dbus 1.2.0-3
python-dbus-common 1.2.0-3
python2-dbus 1.2.0-3
systemd 212-1
systemd-sysvcompat 212-1

Someone please, save my life.

-- 
Best Regards,
Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
Finger Print:   9F67 391B B770 8FF6 99DC  D92D 87F6 2602 1371 4D33