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             | bionic           |

But before you'd be able to upgrade to Focal (do-release-upgrade will otherwise 
block) that would even in Bionic be upgraded to 2.4.3-1ubuntu3.18.04.3
 libseccomp2 | 2.4.3-1ubuntu3.18.04.3       | bionic-security  |
 libseccomp2 | 2.4.3-1ubuntu3.18.04.3       | bionic-updates   |

On that upgrade these files would vanish.

I've taken a Bionic system, downgraded to 2.3.1-2.1ubuntu4 and from there 
upgraded the package.
The files went away as one would expect:

root@b:~# ll /lib/x86_64-linux-gnu/libseccomp.so*
lrwxrwxrwx 1 root root     19 Mar  1  2018 
/lib/x86_64-linux-gnu/libseccomp.so.2 -> libseccomp.so.2.3.1
-rw-r--r-- 1 root root 280776 Mar  1  2018 
/lib/x86_64-linux-gnu/libseccomp.so.2.3.1
root@b:~# apt install libseccomp2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  libseccomp2
1 upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
Need to get 42.0 kB of archives.
After this operation, 29.7 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libseccomp2 
amd64 2.4.3-1ubuntu3.18.04.3 [42.0 kB]
Fetched 42.0 kB in 0s (312 kB/s)       
(Reading database ... 43328 files and directories currently installed.)
Preparing to unpack .../libseccomp2_2.4.3-1ubuntu3.18.04.3_amd64.deb ...
Unpacking libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.3) over (2.3.1-2.1ubuntu4) ...
Setting up libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.3) ...
Processing triggers for libc-bin (2.27-3ubuntu1.2) ...
root@b:~# ll /lib/x86_64-linux-gnu/libseccomp.so*
lrwxrwxrwx 1 root root     19 Jun 29 12:52 
/lib/x86_64-linux-gnu/libseccomp.so.2 -> libseccomp.so.2.4.3
-rw-r--r-- 1 root root 309456 Jun 29 12:52 
/lib/x86_64-linux-gnu/libseccomp.so.2.4.3


Do you have any chance (backup, snapshot or anything) to check which package 
(if any) owned these files on your Bionic system before upgrade?

Furthermore from your system it might be interesting to get /var/log/dpkg.log* 
attached here.
Not sure one can find something in there, but we could track exactly what 
happened to your libseccomp2 in the past - maybe that reconstruction helps to 
find how/why these files got left on your disk.

-- 
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:
  Kernel panic booting after 18.04 to 20.04 upgrade

Status in libseccomp package in Ubuntu:
  Incomplete

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

Reply via email to