[Touch-packages] [Bug 2100501] Re: systemctl daemon-reload makes systemd crash

2025-03-18 Thread Nick Rosbrook
This is what I see re-tracing the crash: root@jammy:~# apport-retrace --gdb _usr_lib_systemd_systemd.0.crash GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free sof

[Touch-packages] [Bug 2100501] Re: systemctl daemon-reload makes systemd crash

2025-03-15 Thread Marcus Kool
I see that the status is still 'incomplete'. Do you need more information? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2100501 Title: systemctl daemon-reload makes syst

[Touch-packages] [Bug 2100501] Re: systemctl daemon-reload makes systemd crash

2025-03-06 Thread Marcus Kool
crash file provided ** Changed in: systemd (Ubuntu Jammy) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2100501 Title: systemctl daemon-

[Touch-packages] [Bug 2100501] Re: systemctl daemon-reload makes systemd crash

2025-03-04 Thread Marcus Kool
The systemd crash has now happened 4 times over the last couple of months. We use systemctl sporadically and I do not recall if all crashes were caused by 'systemctl daemon-reload' so I cannot deny nor confirm that it is reproducible. There is a crash file. It can be downloaded here: https://fil

[Touch-packages] [Bug 2100501] Re: systemctl daemon-reload makes systemd crash

2025-03-04 Thread Nick Rosbrook
Is this sporadic then? Or reproducible under some circumstances? And is there a crash file for systemd under /var/crash? That would hopefully have a stack trace which would make this easier to debug. ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in