Bug#770644: marked as done (systemd: systemd is completely unusable after a fatal signal)

[Debian Bug Tracking System]

Your message dated Wed, 30 Sep 2015 23:39:13 +0200
with message-id <560C5681.4070402 at debian.org>
and subject line Re: Bug#770644: systemd: can't start dbus if dbus is not running
has caused the Debian Bug report #770644,
regarding systemd: systemd is completely unusable after a fatal signal
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
770644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770644
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: "brian m. carlson" <sandals at crustytoothpaste.net>
Subject: systemd: can't start dbus if dbus is not running
Date: Sat, 22 Nov 2014 21:34:03 +0000
Size: 5539
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150930/d1ae718b/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#770644: systemd: can't start dbus if dbus is not running
Date: Wed, 30 Sep 2015 23:39:13 +0200
Size: 4484
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150930/d1ae718b/attachment-0001.mht>