On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: > > 2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>: > >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl <bi...@debian.org>: > >>>> Hi, > >>>> > >>>> I just uploaded v236 today. Before we try to debug this further, it > >>>> would be great if you can give this version a try. Maybe your issue is > >>>> already fixed. > >>>> If not, we'll have to involve upstream at some point by filing an > >>>> upstream bug report. But let's first wait for your results with 236-1 > >>> > >>> The issue is not fixed. Something fails at communicating with dbus, > >>> and it messes up everything else. > >> > >> Just to be sure, have you rebooted your system after upgrading to 236-1? > > > > Yes I have, but this required issuing "exec reboot -f" to bypass init > > entirely, otherwise it fails due to the lack of dbus connection. > > Sure, if PID 1 has crashed, it will freeze itself and no longer respond > to any (D-Bus) requests. > > When exactly does systemd crash? Is it immediately during boot or after > you've been using the system for a while? > I assume it works at least for a while, otherwise no other services > would be started and you would not be able to log in. > When systemd crashes, you should get an entry in the kernel log (dmesg) > respectively the journal. > > It would be great if you can follow the instructions at [1] to boot with > debug logging enabled and then provide a journal log which shows such a > crash. >
Any updates on this? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
