[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system
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 the discussions many have tried to recreate it with those steps but it was not triggering for further debugging. Just to be sure I did try to recreate again in a new clean system (this time direct upgrades, no do-release-upgrade) upgrading X-B-F => no issues. I also rechecked the libseccomp.so files - always had only those belonging to the current installed version. As you can see the open question is either: a) find the details to the steps to really recreate this or b) finding out where the older files came from as they have in none of the case been part of the system that was upgraded from but from somewhere further in the past. -- 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: systemd breaks due to old libsecomp libs left on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system
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 error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get 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: Start with 16.04 upgrade to 18.04 and then 20.04. Clearly the upgrade tool is not properly cleaning up these files. -- 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: systemd breaks due to old libsecomp libs left on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system
[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. https://bugs.launchpad.net/bugs/1876486 Title: systemd breaks due to old libsecomp libs left on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system
** 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: systemd breaks due to old libsecomp libs left on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
