Bug#770644: systemd: can't start dbus if dbus is not running

[Michael Biebl]

Am 08.03.2015 um 15:30 schrieb brian m. carlson:
> On Sat, Mar 07, 2015 at 12:47:33AM +0100, Michael Biebl wrote:
>> Can you provide steps how this issue can be reproduced?
> 
> Actually, I just discovered a set of steps on how to reproduce this:
> 
>   Run kill -s ABRT 1
>   Run telinit u
>   Suspend the machine (possibly multiple times)
> 
> When the machine unsuspends, systemd will no longer be responding to 
> service commands.  Also, on a laptop, Network Manager will work, 
> although the applet will indicate it's not connected.
> 

That systemd freezes when it dies is expected behaviour and the only
real sensible thing to do. At this point, you can only reboot, to get
back into a defined state. You'll need reboot -f here, which bypasses init.

What I was interested in, when I was asking about steps to reproduce
this issue, is how the crash was triggered.
I know that I can kill systemd via "kill -s ABRT 1", but that was not
the point of my question.

I'm interested the cause for the crash.


Regards,
Michael




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150320/fb34f015/attachment-0002.sig>