Ubuntu 18.04 upgraded from 16.04 cannot load upowerd, cannot find libssl.so.1.0.2

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite
1












I ran 16.04 since it was released as a fresh install, and about a month ago upgraded to 18.04 using the official upgrade mechanism. I've noticed this in syslog:



Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[836]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object fil
e: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 1.
Sep 27 17:40:36 yavin systemd[1]: Stopped Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[846]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 2.


So upowerd cannot find libssl.so.1.0.2, sure enough:



$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


Is upowerd still used in 18.04, and if so, how can I confirm which versions of it and libssl/libcrypto I have, which I need, and perhaps forcably re-install them?



Here's what I seem to have installed:



$ sudo apt list --installed | grep "libssl"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl-dev/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]
libssl-doc/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 all [installed,local]
libssl1.0.0/bionic-updates,bionic-security,now 1.0.2n-1ubuntu5.1 amd64 [installed]
libssl1.1/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]


And libcrypto:



$ sudo apt list --installed | grep "crypto"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libblockdev-crypto2/bionic,now 2.16-2 amd64 [installed]
libhcrypto4-heimdal/bionic,now 7.5.0+dfsg-1 amd64 [installed]
libk5crypto3/bionic,now 1.16-2build1 amd64 [installed,automatic]
python-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed,automatic]
python3-asn1crypto/bionic,bionic,now 0.24.0-1 all [installed]
python3-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed]
python3-cryptography/bionic-updates,bionic-security,now 2.1.4-1ubuntu1.2 amd64 [installed]


This may have been a problem since before the upgrade. Without upowerd I have no battery level management and my laptop has powered down suddenly losing work a couple of times and I recall this happening before the upgrade also.



EDIT



As requested, output of apt policy upower:



upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


EDIT 2



Asking apt to reinstall upower results in the same package being installed, and no change in apt policy upower output.



$ sudo apt install --reinstall upower
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 45 not upgraded.
Need to get 102 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 upower amd64 0.99.7-2 [102 kB]
Fetched 102 kB in 0s (381 kB/s)
(Reading database ... 283627 files and directories currently installed.)
Preparing to unpack .../upower_0.99.7-2_amd64.deb ...
Unpacking upower (0.99.7-2) over (0.99.7-2) ...
Setting up upower (0.99.7-2) ...
upower.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...

$ sudo apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


No diversions seem to be set up, and the libssl and libcrypto libraries are still not found by the upowerd binary:



$ dpkg-divert --list /usr/lib/upower/upowerd

$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


EDIT adding comparison with fresh install of Ubuntu 18.04



Since @stephen-kitt mentioned upowerd isn't supposed to depend on libssl, I installed a fresh virtual machine with 18.04 and sure enough, the ldd list is different.



laptop with problem except from ldd -v /usr/lib/upower/upowerd



ibffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ff3f0466000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff3f01f5000)
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007ff3effed000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff3f2f14000)


fresh 18.04 install



libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f4aa91de000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4aa8f6c000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f4aa8c07000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f4aa89f4000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f4aa86d9000)
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007f4aa84d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4aabc8c000)


For some reason the laptop links against libssl and libcrypto, while fresh install links to libgnutls, libtasn1 and libgcrypt.



The fresh install still reports the same apt policy as the laptop:



$ apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


I've no idea why this might be.



Pretty soon I'm just going to reinstall the laptop (it has other issues like very long delays in apps like gedit loading) but it would be nice to figure out how this mess happened.










share|improve this question























  • What does apt policy upower output?
    – Stephen Kitt
    Sep 28 at 4:44










  • I've added it to the question. It's not a command I've seen before.
    – Neek
    Sep 28 at 9:45











  • That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
    – Stephen Kitt
    Oct 1 at 7:36















up vote
0
down vote

favorite
1












I ran 16.04 since it was released as a fresh install, and about a month ago upgraded to 18.04 using the official upgrade mechanism. I've noticed this in syslog:



Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[836]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object fil
e: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 1.
Sep 27 17:40:36 yavin systemd[1]: Stopped Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[846]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 2.


So upowerd cannot find libssl.so.1.0.2, sure enough:



$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


Is upowerd still used in 18.04, and if so, how can I confirm which versions of it and libssl/libcrypto I have, which I need, and perhaps forcably re-install them?



Here's what I seem to have installed:



$ sudo apt list --installed | grep "libssl"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl-dev/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]
libssl-doc/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 all [installed,local]
libssl1.0.0/bionic-updates,bionic-security,now 1.0.2n-1ubuntu5.1 amd64 [installed]
libssl1.1/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]


And libcrypto:



$ sudo apt list --installed | grep "crypto"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libblockdev-crypto2/bionic,now 2.16-2 amd64 [installed]
libhcrypto4-heimdal/bionic,now 7.5.0+dfsg-1 amd64 [installed]
libk5crypto3/bionic,now 1.16-2build1 amd64 [installed,automatic]
python-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed,automatic]
python3-asn1crypto/bionic,bionic,now 0.24.0-1 all [installed]
python3-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed]
python3-cryptography/bionic-updates,bionic-security,now 2.1.4-1ubuntu1.2 amd64 [installed]


This may have been a problem since before the upgrade. Without upowerd I have no battery level management and my laptop has powered down suddenly losing work a couple of times and I recall this happening before the upgrade also.



EDIT



As requested, output of apt policy upower:



upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


EDIT 2



Asking apt to reinstall upower results in the same package being installed, and no change in apt policy upower output.



$ sudo apt install --reinstall upower
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 45 not upgraded.
Need to get 102 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 upower amd64 0.99.7-2 [102 kB]
Fetched 102 kB in 0s (381 kB/s)
(Reading database ... 283627 files and directories currently installed.)
Preparing to unpack .../upower_0.99.7-2_amd64.deb ...
Unpacking upower (0.99.7-2) over (0.99.7-2) ...
Setting up upower (0.99.7-2) ...
upower.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...

$ sudo apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


No diversions seem to be set up, and the libssl and libcrypto libraries are still not found by the upowerd binary:



$ dpkg-divert --list /usr/lib/upower/upowerd

$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


EDIT adding comparison with fresh install of Ubuntu 18.04



Since @stephen-kitt mentioned upowerd isn't supposed to depend on libssl, I installed a fresh virtual machine with 18.04 and sure enough, the ldd list is different.



laptop with problem except from ldd -v /usr/lib/upower/upowerd



ibffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ff3f0466000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff3f01f5000)
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007ff3effed000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff3f2f14000)


fresh 18.04 install



libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f4aa91de000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4aa8f6c000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f4aa8c07000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f4aa89f4000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f4aa86d9000)
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007f4aa84d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4aabc8c000)


For some reason the laptop links against libssl and libcrypto, while fresh install links to libgnutls, libtasn1 and libgcrypt.



The fresh install still reports the same apt policy as the laptop:



$ apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


I've no idea why this might be.



Pretty soon I'm just going to reinstall the laptop (it has other issues like very long delays in apps like gedit loading) but it would be nice to figure out how this mess happened.










share|improve this question























  • What does apt policy upower output?
    – Stephen Kitt
    Sep 28 at 4:44










  • I've added it to the question. It's not a command I've seen before.
    – Neek
    Sep 28 at 9:45











  • That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
    – Stephen Kitt
    Oct 1 at 7:36













up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I ran 16.04 since it was released as a fresh install, and about a month ago upgraded to 18.04 using the official upgrade mechanism. I've noticed this in syslog:



Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[836]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object fil
e: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 1.
Sep 27 17:40:36 yavin systemd[1]: Stopped Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[846]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 2.


So upowerd cannot find libssl.so.1.0.2, sure enough:



$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


Is upowerd still used in 18.04, and if so, how can I confirm which versions of it and libssl/libcrypto I have, which I need, and perhaps forcably re-install them?



Here's what I seem to have installed:



$ sudo apt list --installed | grep "libssl"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl-dev/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]
libssl-doc/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 all [installed,local]
libssl1.0.0/bionic-updates,bionic-security,now 1.0.2n-1ubuntu5.1 amd64 [installed]
libssl1.1/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]


And libcrypto:



$ sudo apt list --installed | grep "crypto"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libblockdev-crypto2/bionic,now 2.16-2 amd64 [installed]
libhcrypto4-heimdal/bionic,now 7.5.0+dfsg-1 amd64 [installed]
libk5crypto3/bionic,now 1.16-2build1 amd64 [installed,automatic]
python-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed,automatic]
python3-asn1crypto/bionic,bionic,now 0.24.0-1 all [installed]
python3-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed]
python3-cryptography/bionic-updates,bionic-security,now 2.1.4-1ubuntu1.2 amd64 [installed]


This may have been a problem since before the upgrade. Without upowerd I have no battery level management and my laptop has powered down suddenly losing work a couple of times and I recall this happening before the upgrade also.



EDIT



As requested, output of apt policy upower:



upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


EDIT 2



Asking apt to reinstall upower results in the same package being installed, and no change in apt policy upower output.



$ sudo apt install --reinstall upower
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 45 not upgraded.
Need to get 102 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 upower amd64 0.99.7-2 [102 kB]
Fetched 102 kB in 0s (381 kB/s)
(Reading database ... 283627 files and directories currently installed.)
Preparing to unpack .../upower_0.99.7-2_amd64.deb ...
Unpacking upower (0.99.7-2) over (0.99.7-2) ...
Setting up upower (0.99.7-2) ...
upower.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...

$ sudo apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


No diversions seem to be set up, and the libssl and libcrypto libraries are still not found by the upowerd binary:



$ dpkg-divert --list /usr/lib/upower/upowerd

$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


EDIT adding comparison with fresh install of Ubuntu 18.04



Since @stephen-kitt mentioned upowerd isn't supposed to depend on libssl, I installed a fresh virtual machine with 18.04 and sure enough, the ldd list is different.



laptop with problem except from ldd -v /usr/lib/upower/upowerd



ibffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ff3f0466000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff3f01f5000)
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007ff3effed000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff3f2f14000)


fresh 18.04 install



libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f4aa91de000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4aa8f6c000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f4aa8c07000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f4aa89f4000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f4aa86d9000)
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007f4aa84d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4aabc8c000)


For some reason the laptop links against libssl and libcrypto, while fresh install links to libgnutls, libtasn1 and libgcrypt.



The fresh install still reports the same apt policy as the laptop:



$ apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


I've no idea why this might be.



Pretty soon I'm just going to reinstall the laptop (it has other issues like very long delays in apps like gedit loading) but it would be nice to figure out how this mess happened.










share|improve this question















I ran 16.04 since it was released as a fresh install, and about a month ago upgraded to 18.04 using the official upgrade mechanism. I've noticed this in syslog:



Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[836]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object fil
e: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 1.
Sep 27 17:40:36 yavin systemd[1]: Stopped Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: Starting Daemon for power management...
Sep 27 17:40:36 yavin upowerd[846]: /usr/lib/upower/upowerd: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Sep 27 17:40:36 yavin systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
Sep 27 17:40:36 yavin systemd[1]: upower.service: Failed with result 'exit-code'.
Sep 27 17:40:36 yavin systemd[1]: Failed to start Daemon for power management.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Service hold-off time over, scheduling restart.
Sep 27 17:40:36 yavin systemd[1]: upower.service: Scheduled restart job, restart counter is at 2.


So upowerd cannot find libssl.so.1.0.2, sure enough:



$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


Is upowerd still used in 18.04, and if so, how can I confirm which versions of it and libssl/libcrypto I have, which I need, and perhaps forcably re-install them?



Here's what I seem to have installed:



$ sudo apt list --installed | grep "libssl"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl-dev/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]
libssl-doc/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 all [installed,local]
libssl1.0.0/bionic-updates,bionic-security,now 1.0.2n-1ubuntu5.1 amd64 [installed]
libssl1.1/now 1.1.0h-2.0+ubuntu16.04.1+deb.sury.org+1 amd64 [installed,local]


And libcrypto:



$ sudo apt list --installed | grep "crypto"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libblockdev-crypto2/bionic,now 2.16-2 amd64 [installed]
libhcrypto4-heimdal/bionic,now 7.5.0+dfsg-1 amd64 [installed]
libk5crypto3/bionic,now 1.16-2build1 amd64 [installed,automatic]
python-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed,automatic]
python3-asn1crypto/bionic,bionic,now 0.24.0-1 all [installed]
python3-crypto/bionic,now 2.6.1-8ubuntu2 amd64 [installed]
python3-cryptography/bionic-updates,bionic-security,now 2.1.4-1ubuntu1.2 amd64 [installed]


This may have been a problem since before the upgrade. Without upowerd I have no battery level management and my laptop has powered down suddenly losing work a couple of times and I recall this happening before the upgrade also.



EDIT



As requested, output of apt policy upower:



upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


EDIT 2



Asking apt to reinstall upower results in the same package being installed, and no change in apt policy upower output.



$ sudo apt install --reinstall upower
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 45 not upgraded.
Need to get 102 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 upower amd64 0.99.7-2 [102 kB]
Fetched 102 kB in 0s (381 kB/s)
(Reading database ... 283627 files and directories currently installed.)
Preparing to unpack .../upower_0.99.7-2_amd64.deb ...
Unpacking upower (0.99.7-2) over (0.99.7-2) ...
Setting up upower (0.99.7-2) ...
upower.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...

$ sudo apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://ubuntu.ipserverone.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


No diversions seem to be set up, and the libssl and libcrypto libraries are still not found by the upowerd binary:



$ dpkg-divert --list /usr/lib/upower/upowerd

$ ldd -v /usr/lib/upower/upowerd | grep 'not found'
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libcrypto.so.1.0.2 (OPENSSL_1.0.2d) => not found
libssl.so.1.0.2 (OPENSSL_1.0.2d) => not found


EDIT adding comparison with fresh install of Ubuntu 18.04



Since @stephen-kitt mentioned upowerd isn't supposed to depend on libssl, I installed a fresh virtual machine with 18.04 and sure enough, the ldd list is different.



laptop with problem except from ldd -v /usr/lib/upower/upowerd



ibffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ff3f0466000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff3f01f5000)
libssl.so.1.0.2 => not found
libcrypto.so.1.0.2 => not found
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007ff3effed000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff3f2f14000)


fresh 18.04 install



libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f4aa91de000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4aa8f6c000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f4aa8c07000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f4aa89f4000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f4aa86d9000)
libusbmuxd.so.4 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 (0x00007f4aa84d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4aabc8c000)


For some reason the laptop links against libssl and libcrypto, while fresh install links to libgnutls, libtasn1 and libgcrypt.



The fresh install still reports the same apt policy as the laptop:



$ apt policy upower
upower:
Installed: 0.99.7-2
Candidate: 0.99.7-2
Version table:
*** 0.99.7-2 500
500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


I've no idea why this might be.



Pretty soon I'm just going to reinstall the laptop (it has other issues like very long delays in apps like gedit loading) but it would be nice to figure out how this mess happened.







ubuntu ssl






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago

























asked Sep 28 at 3:39









Neek

15114




15114











  • What does apt policy upower output?
    – Stephen Kitt
    Sep 28 at 4:44










  • I've added it to the question. It's not a command I've seen before.
    – Neek
    Sep 28 at 9:45











  • That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
    – Stephen Kitt
    Oct 1 at 7:36

















  • What does apt policy upower output?
    – Stephen Kitt
    Sep 28 at 4:44










  • I've added it to the question. It's not a command I've seen before.
    – Neek
    Sep 28 at 9:45











  • That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
    – Stephen Kitt
    Oct 1 at 7:36
















What does apt policy upower output?
– Stephen Kitt
Sep 28 at 4:44




What does apt policy upower output?
– Stephen Kitt
Sep 28 at 4:44












I've added it to the question. It's not a command I've seen before.
– Neek
Sep 28 at 9:45





I've added it to the question. It's not a command I've seen before.
– Neek
Sep 28 at 9:45













That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
– Stephen Kitt
Oct 1 at 7:36





That’s really weird, mostly because upowerd isn’t supposed to have a dependency on libssl or libcrypto (I checked the Ubuntu package too); does ls -l /usr/lib/upower/upowerd show that your binary dates from January 30, 2018? Could you edit your question (again...) to show the full output of ldd /usr/lib/upower/upowerd (without the -v, that shouldn’t have any impact here)?
– Stephen Kitt
Oct 1 at 7:36











1 Answer
1






active

oldest

votes

















up vote
2
down vote













Somehow you’ve ended up with a version of /usr/lib/upower/upowerd which doesn’t correspond to the file contained in the upower package.



To fix this, re-install the package:



sudo apt install --reinstall upower


If that doesn’t help, check whether there are any diversions:



dpkg-divert --list /usr/lib/upower/upowerd


If that shows a diversion, check the corresponding package; you might need to upgrade or remove it.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471974%2fubuntu-18-04-upgraded-from-16-04-cannot-load-upowerd-cannot-find-libssl-so-1-0%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    Somehow you’ve ended up with a version of /usr/lib/upower/upowerd which doesn’t correspond to the file contained in the upower package.



    To fix this, re-install the package:



    sudo apt install --reinstall upower


    If that doesn’t help, check whether there are any diversions:



    dpkg-divert --list /usr/lib/upower/upowerd


    If that shows a diversion, check the corresponding package; you might need to upgrade or remove it.






    share|improve this answer
























      up vote
      2
      down vote













      Somehow you’ve ended up with a version of /usr/lib/upower/upowerd which doesn’t correspond to the file contained in the upower package.



      To fix this, re-install the package:



      sudo apt install --reinstall upower


      If that doesn’t help, check whether there are any diversions:



      dpkg-divert --list /usr/lib/upower/upowerd


      If that shows a diversion, check the corresponding package; you might need to upgrade or remove it.






      share|improve this answer






















        up vote
        2
        down vote










        up vote
        2
        down vote









        Somehow you’ve ended up with a version of /usr/lib/upower/upowerd which doesn’t correspond to the file contained in the upower package.



        To fix this, re-install the package:



        sudo apt install --reinstall upower


        If that doesn’t help, check whether there are any diversions:



        dpkg-divert --list /usr/lib/upower/upowerd


        If that shows a diversion, check the corresponding package; you might need to upgrade or remove it.






        share|improve this answer












        Somehow you’ve ended up with a version of /usr/lib/upower/upowerd which doesn’t correspond to the file contained in the upower package.



        To fix this, re-install the package:



        sudo apt install --reinstall upower


        If that doesn’t help, check whether there are any diversions:



        dpkg-divert --list /usr/lib/upower/upowerd


        If that shows a diversion, check the corresponding package; you might need to upgrade or remove it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 28 at 9:56









        Stephen Kitt

        149k23328396




        149k23328396



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471974%2fubuntu-18-04-upgraded-from-16-04-cannot-load-upowerd-cannot-find-libssl-so-1-0%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay