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 Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: systemd breaks due to old libsecomp libs left on the system Status in libseccomp package in Ubuntu: Expired Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [ 4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
