[Pkg-utopia-maintainers] Bug#930539: upowerd cannot start due to searching the wrong libssl version

[Andreas v. Heydwolff]

Thanks, Andrey
On 01.07.19 16:02, Andrey Rahmatullin wrote:
> On Fri, Jun 14, 2019 at 10:16:50PM +0200, A. Heydwolff wrote:
>> Jun 14 21:10:58 karfiol upowerd[15367]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
> Note that /usr/lib/upower/upowerd isn't linked to libssl directly, and, at
> least in sid, not even indirectly. This means there is some problem with
> one of the libraries it loads and, I suspect, it's a library installed
> locally.
> You can start debugging this with ldd (or just looking into /usr/local).

Thanks, Andrey!

Using ldd I see again what systemd showed me:

 libssl.so.1.0.0 => *not found*
 libcrypto.so.1.0.0 => *not found*

Would one of the other libs that can be found in the output try to load
them:

# ldd /usr/lib/upower/upowerd
        linux-vdso.so.1 (0x00007ffd4d3f3000)
        libupower-glib.so.3 =>
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3 (0x00007f0eedce2000)
        libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x00007f0eed94c000)
        libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0
(0x00007f0eed733000)
        libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0
(0x00007f0eed529000)
        libgobject-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f0eed2d6000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007f0eecfc2000)
        libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6
(0x00007f0eecd9c000)
        libplist.so.3 => /usr/lib/x86_64-linux-gnu/libplist.so.3
(0x00007f0eecb8d000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f0eecb6c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0eec9af000)
        libgmodule-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f0eec7ab000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0eec591000)
        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
(0x00007f0eec367000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
(0x00007f0eec34e000)
        libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
(0x00007f0eec100000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1
(0x00007f0eebedb000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
(0x00007f0eebcd2000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
(0x00007f0eeba5f000)
        libssl.so.1.0.0 => *not found*
        libcrypto.so.1.0.0 => *not found*
        libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4
(0x00007f0eeb855000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0eedd76000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0eeb850000)
        libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
(0x00007f0eeb60a000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0eeb5fe000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
(0x00007f0eeb5f5000)

- or is my libc6 too old to work together with the latest upowerd (on
Stretch with stretch-backports).

# file /usr/lib/upower/upowerd
/usr/lib/upower/upowerd: ELF 64-bit LSB shared object, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 3.2.0, BuildID[sha1]=a1b060672d26001064a495a1dab0fbfb002ce8ef,
stripped

# ls -l /lib64/ld-linux-x86-64.so.2
[...] /lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.27.so

# dpkg -l libc6
+++-================================-=====================-=====================-======================================================================
ii  libc6:amd64                      2.27-6                amd64


> 
>> Installed are 
>> -rw-r--r-- 1 root root 349K Oct  7  2017 libssl3.so
>> -rw-r--r-- 1 root root 422K Feb 27 21:58 libssl.so.1.0.2
>> -rw-r--r-- 1 root root 576K Apr 16 21:31 libssl.so.1.1
>>
>> I created a 1.0.0 symlink to 1.0.2
> Never do this.

Of course not ... but I deleted it immediately after having used it for
the very clumsy attempt at diagnostics. ldd would have been the better
choice in first place ...

Regards