systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[André]

This happened when trying to upgrade from 21.04 to 21.10.

Setting up systemd (248.3-1ubuntu2) ...
systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 127
Processing triggers for initramfs-tools (0.140ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
Processing triggers for libc-bin (2.33-0ubuntu7) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.20-2ubuntu1) ...
Errors were encountered while processing:
 systemd

I reverted to old version by manualing installing the hirsute's debs (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb systemd_247.3-3ubuntu3.4_amd64.deb libnss-systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb libpam-systemd_247.3-3ubuntu3.4_amd64.deb libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-dev_247.3-3ubuntu3.4_amd64.deb)

[André (afsverissimo)]

Problem persists while trying to upgrade to newer version of package (248.3-1ubuntu3)

(Reading database ... 769323 files and directories currently installed.)
Preparing to unpack .../libsystemd-dev_248.3-1ubuntu3_amd64.deb ...
Unpacking libsystemd-dev:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libnss-systemd_248.3-1ubuntu3_amd64.deb ...
Unpacking libnss-systemd:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libudev-dev_248.3-1ubuntu3_amd64.deb ...
Unpacking libudev-dev:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libudev1_248.3-1ubuntu3_amd64.deb ...
Unpacking libudev1:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Setting up libudev1:amd64 (248.3-1ubuntu3) ...
(Reading database ... 769328 files and directories currently installed.)
Preparing to unpack .../systemd_248.3-1ubuntu3_amd64.deb ...
Unpacking systemd (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../udev_248.3-1ubuntu3_amd64.deb ...
Unpacking udev (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libsystemd0_248.3-1ubuntu3_i386.deb ...
De-configuring libsystemd0:amd64 (247.3-3ubuntu3.4) ...
Unpacking libsystemd0:i386 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libsystemd0_248.3-1ubuntu3_amd64.deb ...
Unpacking libsystemd0:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Setting up libsystemd0:amd64 (248.3-1ubuntu3) ...
Setting up systemd (248.3-1ubuntu3) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/networkd.conf ...
Installing new version of config file /etc/systemd/pstore.conf ...
Installing new version of config file /etc/systemd/resolved.conf ...
Installing new version of config file /etc/systemd/sleep.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version of config file /etc/systemd/user.conf ...
systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot ope
n shared object file: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

[André (afsverissimo)]

This was a byproduct of a incomplete usrmerge

Calling the binary below and solving the problems fixed the issue

/usr/lib/usrmerge/convert-usrmerge

[DarkTrick (darktrick1337)]

I set it to new. I had the same problem. I feel this should be universally solved.

Related question: https://askubuntu.com/questions/1379811/usrmerge-of-bin-sbin-lib-how-is-the-system-supposed-to-be

Perhaps related bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945582

- Is `/usr/lib/usrmerge/convert-usrmerge` really the solution users are supposed to run?
- Some systems have the whole directory /bin linked to /usr/bin, this is not what convert-usrmerge appears to do. This inconsistence should be explained and the "right" solution should be announced.

I worked around my failing upgrade via
- edit `/var/lib/dpkg/info/systemd.postinst` by hand
- find the line `systemd-machine-id-setup`
- comment it out
- run `sudo dpkg --configure -a` again

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nick Rosbrook (enr0n)]

This version of systemd is no longer in any supported Ubuntu release.