Actually, that makes a surprising amount of sense. Surely, when you cause dbus to start upowerd on demand, upowerd should be possible to manage through systemd like any other daemon, right? I mean, it's not like it's part of dbus, despite dbus launching it. Sure, it's reasonable for dbus to handle demand-execution of services when your init isn't capable of that, but having dbus be a second process launcher when you've already got one is redundant and just makes management harder.