Hmm thanks Raphaël.
So files were still around that were unowned, that really should not happen.
Thanks for the exact file names.
The files you had in your case were part of libseccomp2 2.3.1-2.1ubuntu4 which
is what Ubuntu had in Bionic-release.
libseccomp2 | 2.3.1-2.1ubuntu4 |
I'm in the same case as Joi: I went from Ubuntu 16.04 to Ubuntu 18.04 to
Ubuntu 20.04. Removing libsecomp libraries in /lib and the old one in
/usr/lib (version 2.3) allowed the system to boot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
These files didn't belong to any package (anymore?). Here are the files I
removed:
- /lib/x86_64-linux-gnu/libseccomp.so.2.3.1
- /lib/x86_64-linux-gnu/libseccomp.so.2 (link to the previous file)
- /usr/lib/x86_64-linux-gnu/libseccomp.so.2.3.3
--
You received this bug notification because you
Hi Joi,
thanks for the extra data, I still can't think of a case to create this.
Looking forward to what you find checking this in more detail.
When in the error case could you look around which seccomp the system still has
around?
For example via:
$ ls -laF /lib/x86_64-linux-gnu/libseccomp*
I've just encountered this issue myself, on a VM that started life as
Ubuntu 16.04, do-release-upgrade to 18.04, then to 20.04, and now it
fails to boot with a similar error: /lib/systemd/libsystemd-
shared-245.so: undefined symbol: seccomp_api_get
The only non-Ubuntu-standard stuff on this VM
Moving back to incomplete as stated by @paelzer.
** Changed in: libseccomp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libseccomp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Hi,
even Bionic which you upgraded from would have been
/lib/x86_64-linux-gnu/libseccomp.so.2.4.1
2.2 was last available in
libseccomp2 | 2.2.3-2ubuntu1~ubuntu14.04.1 | trusty-backports | amd64, arm64,
armhf, i386, powerpc, ppc64el
libseccomp2 | 2.2.3-3ubuntu3 | xenial
After trying to roll forward again I saw the output from ldconfig
/lib/x86_64-linux-gnu/libseccomp.so.2.2.0 is not a symbolic link
Looks like I had duplicate versions of libseccomp2 lying around on my
LD_LIBRARY_PATH
dpkg -L libseccomp2
/usr/lib/x86_64-linux-gnu/libseccomp.so.2.4.3
So I
This is something to do with linux 5 kernel api
You need to manually downgrade systemd - well - that's what I did.
when you boot with grub or refind - edit default entry and change the
init=/bin/init to init=/bin/bash
That will bypass systemd starting up and drop you straight into a shell.
10 matches
Mail list logo
