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. 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?! Jan 2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18 ip 000055bd29c926ea sp 00007ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000] ls -l /core -rw------- 1 root root 22482944 Jan 2 10:14 /core I can share this core file with you if you wish (how?), though perhaps it's not so related to the upgrade anymore? Christian On Wed, 2022-01-12 at 18:01 +0100, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Hello, > > systemd freezes execution when it crashes (you should see a > corresponding log message in the journal). > > For this bug report to be actionable, we will need at the very least a > backtrace of the crash. > In case you had systemd-coredump installed, coredumpctl should show you. > Or maybe you still have a core file in /. > > > Regards, > Michael >
