[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system

2024-04-29 Thread Christian Ehrhardt 
Hi Jeremy > I do not understand why bugs like this cannot get fixed even years after > several people have reported the same issue and the repro steps are clear I understand this might seem frustrating, but the TL;DR is: Because it isn't as clear as it might seem Detail: As you see throughout

[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system

2024-04-28 Thread Jeremy Akers
I just ran into this same issue. I have a server that started out on 16.04. I just did "do-release-upgrade -m server" to upgrade to 18.04 and then again to 20.04. After the 20.04 upgrade finished the server would no longer boot with the exact same error described here: /sbin/init: symbol lookup

[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system

2020-10-12 Thread Launchpad Bug Tracker
[Expired for libseccomp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libseccomp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system

2020-08-13 Thread Christian Ehrhardt 
** Summary changed: - Kernel panic booting after 18.04 to 20.04 upgrade + systemd breaks due to old libsecomp libs left on the system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: