Bug#903851: dbus does not automatically start after dist-upgrade system stretch with updates from buster

[Simon McVittie]

On Sun, 15 Jul 2018 at 18:00:13 -0400, Thomas Hardman wrote:
> /var/log/syslog is not particularly helpful. `cat syslog |grep "Jul 15 15:" |
> grep dbus` mostly shows success after starting the dbus service by hand with
> `service dbus start`. Perhaps there's some failure to report an error when
> systemd does not successfully start dbus?

Please try looking for other failure messages from systemd, not necessarily
mentioning dbus. When booting with systemd, creating /var/run/dbus is
systemd's responsibility.

Another possible route would be: when you have logged in to recovery mode
or to the emergency shell, run

    dmesg > dmesg.log
    journalctl -l --no-pager -b > journal.log

and look for errors or warnings in dmesg.log or journal.log.

> systemd:amd64 (232-25+deb9u2, 232-25+deb9u4)

It seeems possible that this could be a systemd regression? Or at least,
that seems a more likely trigger than any of the other packages you
mentioned (none of the systemd changes between +deb9u2 and +deb9u4 look
immediately relevant, though).

    smcv