Your message dated Wed, 27 Nov 2019 17:16:35 +0100
with message-id <[email protected]>
and subject line Re: Bug#945582: systemd: Upgrade fails due to missing library
libsystemd-shared-241.so
has caused the Debian Bug report #945582,
regarding systemd: Upgrade fails due to missing library libsystemd-shared-241.so
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
945582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945582
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 243-8
Severity: important
Dear Maintainer,
I am upgrading my debian testing system but the upgrades fail as systemd cannot
be configured.
Output from dpkg --configure systemd:
Setting up systemd (243-8) ...
systemd-machine-id-setup: error while loading shared libraries:
libsystemd-shared-241.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
Errors were encountered while processing:
systemd
I note that ldd /usr/bin/systemd-machine-id-setup tells me:
linux-vdso.so.1 (0x00007fff4bfcb000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa802380000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa802588000)
libsystemd-shared-241.so => not found
/usr/lib/systemd/libsystemd-shared-241.so exists.
ldd /usr/lib/systemd/libsystemd-shared-241.so tells me:
linux-vdso.so.1 (0x00007fffe5d9b000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f73b2e90000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f73b2e88000)
libacl.so.1 => /usr/lib/x86_64-linux-gnu/libacl.so.1
(0x00007f73b2e78000)
libcryptsetup.so.12 => /lib/x86_64-linux-gnu/libcryptsetup.so.12
(0x00007f73b2e08000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20
(0x00007f73b2ce8000)
libip4tc.so.0 => /usr/lib/x86_64-linux-gnu/libip4tc.so.0
(0x00007f73b2cd8000)
libkmod.so.2 => /usr/lib/x86_64-linux-gnu/libkmod.so.2
(0x00007f73b2cb8000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
(0x00007f73b2c50000)
libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2
(0x00007f73b2c00000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
(0x00007f73b2bd0000)
libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x00007f73b2998000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f73b2968000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1
(0x00007f73b2940000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
(0x00007f73b28e8000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f73b28c0000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f73b2700000)
/lib64/ld-linux-x86-64.so.2 (0x00007f73b3170000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f73b26f0000)
libdevmapper.so.1.02.1 => /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
(0x00007f73b2680000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
(0x00007f73b2390000)
libargon2.so.1 => /usr/lib/x86_64-linux-gnu/libargon2.so.1
(0x00007f73b2380000)
libjson-c.so.4 => /usr/lib/x86_64-linux-gnu/libjson-c.so.4
(0x00007f73b2368000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x00007f73b2340000)
libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
(0x00007f73b22b8000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f73b22b0000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f73b2280000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f73b2138000)
I note that my other, not yet upgraded, debian testing system has
systemd-machine-id-setup in /bin (not /usr/bin) and has
libsystemd-shared-241.so in /lib not /usr/lib.
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_IE.utf8), LANGUAGE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to
en_IE.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-5
ii libapparmor1 2.13.3-7
ii libaudit1 1:2.8.5-2+b1
ii libblkid1 2.34-0.1
ii libc6 2.29-3
ii libcap2 1:2.27-1
ii libcryptsetup12 2:2.2.1-1
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.10-5
ii libgpg-error0 1.36-7
ii libidn2-0 2.2.0-2
ii libip4tc2 1.8.3-2
ii libkmod2 26-3
ii liblz4-1 1.9.2-2
ii liblzma5 5.2.4-1+b1
ii libmount1 2.34-0.1
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.32-5+b1
ii libseccomp2 2.4.2-2
ii libselinux1 2.9-3+b1
ii libsystemd0 243-8
ii mount 2.34-0.1
ii util-linux 2.34-0.1
Versions of packages systemd recommends:
ii dbus 1.12.16-2
iu libpam-systemd 243-8
Versions of packages systemd suggests:
ii policykit-1 0.105-26
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.135
ii udev 243-8
-- Configuration Files:
/etc/systemd/journald.conf changed:
SystemMaxUse=4G
SystemKeepFree=4G
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 27.11.19 um 16:22 schrieb Graham Cobb:
> On 27/11/2019 14:05, Ansgar wrote:
>> On Wed, 2019-11-27 at 11:49 +0000, Graham Cobb wrote:
>>> I am upgrading my debian testing system but the upgrades fail as systemd
>>> cannot be configured.
>>>
>>> Output from dpkg --configure systemd:
>>>
>>> Setting up systemd (243-8) ...
>>> systemd-machine-id-setup: error while loading shared libraries:
>>> libsystemd-shared-241.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
>>
>> Hmm, this is strange. When the package is configured, it should
>> already be extracted. And systemd-machine-id-setup from systemd-243
>> shouldn't link against a libsystemd-shared-241.so.
>>
>> You said your system doesn't have merged-/usr, so I wonder why there
>> seems to be /usr/bin/systemd-machine-id-setup and libsystemd-shared-
>> 241.so in /usr.
>>
>> Could you run
>>
>> ls -l /usr/bin/systemd-machine-id-setup \
>> /bin/systemd-machine-id-setup \
>> /usr/lib/systemd/libsystemd-shared* \
>> /lib/systemd/libsystemd-shared*
>
> # ls -l /usr/bin/systemd-machine-id-setup \
>> /bin/systemd-machine-id-setup \
>> /usr/lib/systemd/libsystemd-shared* \
>> /lib/systemd/libsystemd-shared*
> -rwxr-xr-x 1 root root 26792 Nov 19 08:17 /bin/systemd-machine-id-setup
> -rw-r--r-- 1 root root 2806128 Nov 19 08:17
> /lib/systemd/libsystemd-shared-243.so
> -rwxr-xr-x 1 root root 26792 May 24 2019
> /usr/bin/systemd-machine-id-setup
> -rw-r--r-- 1 root root 2670992 May 24 2019
> /usr/lib/systemd/libsystemd-shared-241.so
>
>> I suspect there are some old binaries (from systemd-241) around for
>> some reason.
>
> That does seem to be the case.
>
> I note that dpkg -S can find packages responsible for the /bin
> executables but not the /usr/bin ones:
>
> # dpkg -S /bin/systemd-machine-id-setup
> systemd: /bin/systemd-machine-id-setup
> # dpkg -S /usr/bin/systemd-machine-id-setup
> dpkg-query: no path found matching pattern /usr/bin/systemd-machine-id-setup
>
Thanks for reporting back.
So it seems that some time in the past (around May 2019) you locally
installed v241 into /usr.
You need to manually remove all those files again
I would check the output of dpkg -L systemd and remove all duplicates
from /usr/bin and /usr/lib for files in /bin and /lib.
Check if the files from dpkg -L systemd | grep -E '^(/lib|/bin)'
have a duplicate in in /usr and if so, remove those duplicates.
In any case, this is not a bug in the Debian package, so closing this
bug report.
Still curious how this happend.
Have you manually compiled systemd in the past?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
