Am 12.01.22 um 18:20 schrieb Christian Weeks:
I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.

Once PID 1 has been frozen, you can't reactivate it. dbus tried to talk to it but eventually timed out. dbus is not supposed to "start" PID1.

The only option to recover from such a scenario is to reboot (forcefully) as you did.

I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!

I'd say this observation is correct.

If you still have the journal, maybe attach the preceeding 10 mins before the crash, i.e. all log messages from
Jan  2 10:00:00 until  Jan  2 10:14:48

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to