On Sat, May 13, 2017 at 05:29:13PM +0200, Michael Biebl babbled thus:
> But this is systemd-logind, not systemd, which doesn't respond.
> And apparently systemd is still active, otherwise it couldn't kill the
> non-responsing systemd-logind process.
>
> Where exactly does systemd crash? Where is
Control: tags -1 + moreinfo
Am 13.05.2017 um 16:48 schrieb Mike Edwards:
> Package: systemd
> Version: 232-23
> Severity: critical
> Justification: causes serious data loss
>
> * Note that this report applies to 232-22 - I just did an apt upgrade
> immediately before filing this bug report.
>
>
Processing control commands:
> tags -1 + moreinfo
Bug #862490 [systemd] systemd 232-22 hangs with watchdog timeout, kills self
with SIGABRT
Added tag(s) moreinfo.
--
862490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
3 matches
Mail list logo