On Thu, Sep 29, 2011 at 04:03:48PM +0200, Michael Biebl wrote: > Am 25.09.2011 09:18, schrieb Josh Triplett: > > On Sun, Sep 25, 2011 at 02:02:18AM +0200, Michael Biebl wrote: > >> Am 24.09.2011 23:19, schrieb Josh Triplett: > >>> process 26353: arguments to dbus_connection_send_with_reply_and_block() > >>> were incorrect, assertion "connection != NULL" failed in file > >>> ../../dbus/dbus-connection.c line 3483. > >>> This is normally a bug in some application using the D-Bus library. > >>> Failed to issue method call: (null) > >>> > >>> I'd guess this comes from the call to "systemctl daemon-reexec" in the > >>> postinst. Please consider checking for systemd first, or changing > >>> systemctl to do so. > >> > >> If I understand you correctly, you do have systemd installed but not > >> actually > >> running? > > > > Right. I have it installed, and I can try it out by passing the > > appropriate kernel parameter, but I don't have it set as the default > > init, and I didn't boot with it when I did that upgrade. > > Upstream has committed this patch [1] which returns a proper error message > instead of an assertion.
That's an improvement, but it still looks like an unexpected error. Seems preferable to explicitly say something like "systemd not running". - Josh Triplett -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
