Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-02-20 Thread Michael Biebl
On Wed, 12 Jan 2022 19:54:15 +0100 Michael Biebl wrote: Am 12.01.22 um 19:34 schrieb Christian Weeks: > I have attached the journal from the 10 minutes prior. I was trying to mount a > CD in an external CD rom drive at the time. It seems that something went wrong > and killed systemd. I

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Michael Biebl
Am 12.01.22 um 19:34 schrieb Christian Weeks: I have attached the journal from the 10 minutes prior. I was trying to mount a CD in an external CD rom drive at the time. It seems that something went wrong and killed systemd. I apparently didn't notice for another 10 days. /facepalm I have the

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Christian Weeks
I have attached the journal from the 10 minutes prior. I was trying to mount a CD in an external CD rom drive at the time. It seems that something went wrong and killed systemd. I apparently didn't notice for another 10 days. /facepalm I have the core file, if you want me to analyze it somehow,

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Michael Biebl
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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Michael Biebl
Control: found -1 249.7-1 Control: severity -1 important 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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread 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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Michael Biebl
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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

2022-01-12 Thread Christian Weeks
The reboot fixed the issue - I now have a working computer again, though getting to a reboot was a bit painful. > systemctl reboot Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for