[solved] KDE5 Plasma missing libssl.so.1.0.0

pieterv · 2017-04-24 13:38:22

Since today I cannot start Plasma anymore. I'm getting the error "libssl.so.1.0.0: cannot open shared object file: No such file or directory" during the start of Plasma, from different KDE5 programs. Here's the log:

apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: /etc/gdm/Xsession: Beginning session setup...
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: localuser:user being added to access control list
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/startkde
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: ksplashqml: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: startkde: Starting up...
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: /usr/lib/kf5/klauncher: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directo
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: kdeinit5: Communication error with launcher. Exiting!
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: kdeinit5_wrapper: Warning: connect(/run/user/1001/kdeinit5__0) failed: : Connection refused
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: /usr/bin/ksmserver: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: startkde: Shutting down...
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: kdeinit5_wrapper: Warning: connect(/run/user/1001/kdeinit5__0) failed: : Connection refused
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: Error: Can not contact kdeinit5!
apr 24 14:50:37 arch4 /usr/lib/gdm/gdm-x-session[4117]: startkde: Done.

Indeed, I don't have libssl.so.1.0.0. I only have libssl.so as symlink and libssl.so.1.1:

user@arch ~ $ ls -l /usr/lib/libssl*
-rwxr-xr-x 1 root root 361408 apr  5 22:35 /usr/lib/libssl3.so
lrwxrwxrwx 1 root root     13 feb 16 15:51 /usr/lib/libssl.so -> libssl.so.1.1
-rwxr-xr-x 1 root root 437992 feb 16 15:52 /usr/lib/libssl.so.1.1

My system is up to date.

Current kernel:

user@arch ~ $ uname -a
Linux arch 4.10.11-1-ARCH #1 SMP PREEMPT Tue Apr 18 08:39:42 CEST 2017 x86_64 GNU/Linux

(I also have the LTS kernel, and have the same problem.

Today's update might be relevant?

root@arch4 ~ # grep -i ssl /var/log/pacman.log 
[2017-04-24 14:11] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1

When i manually symlink /usr/lib/libssl.so.1.0.0 to /usr/lib/libssl.so.1.1 it works. I need to symlink als libcrypto.so.1.1 in a similar way. This is of course a temporary fix.
EDIT: the above is a bad idea and shouldn't normally be done. But it was the only thing I could think of to make my laptop boot again, have a graphical interface and network connection in a short time.

Any ideas?

Last edited by pieterv (2017-04-24 14:21:21)

Scimmia · 2017-04-24 13:41:30

Update again, maybe trying a different mirror

When i manually symlink /usr/lib/libssl.so.1.0.0 to /usr/lib/libssl.so.1.1it works. I need to symlink als libcrypto.so.1.1 in a similar way. This is of course a temporary fix.

Not a fix at all, a horrible, horrible hack that could screw up countless things. Don't post shit like that on the forums.

Last edited by Scimmia (2017-04-24 13:44:01)

acottrell · 2017-04-24 13:45:39

Looks like the pacman update from openssl-1.0.2.k to openssl-1.1.0.e was too hasty.
The update (I applied it this morning) removes libcrypto.so.1.0.0 and libssl.so.1.0.0
and thereby breaks a number of packages, including git and gnuplot. Probably lots
of others too.

A workaround is to extract libcrypto.so.1.0.0 and libssl.so.1.0.0 from the previous
openssl archive, openssl-1.0.2.k-1-x86_64.pkg.tar.xz, and install them in /usr/lib.

Last edited by acottrell (2017-04-24 14:16:48)

doskoi · 2017-04-24 13:48:55

There is also the new openssl-1.0 package.

Scimmia · 2017-04-24 13:51:32

acottrell wrote:

ound is to extract ibcrypto.so.1.0.0 and libssl.so.1.0.0 from the previous
openssl archive, openssl-1.0.2.k-1-x86_64.pkg.tar.xz, and install them in /usr/lib.

No, the "workaround" was already posted.

Update....Your....System.

Trilby · 2017-04-24 13:55:03

I just posted in the GRR thread, and there are some related errors in other threads - it looks like the rebuild of packages dependent on openssl may not have gone as smoothly as it normally does/should. A couple packages in the actual repos are funky (ntp got downgraded, presumably accidentally as there was no epoch change) but most problems are likely due to mirrors that synced while the main repos were in a unclean transition state (some packages pushed, others not).

First, check whether your installed package versions match those on the package listing on this website. If they don't, then use a different mirror. If they do, then wait a few minutes

As for the openssl-1.0 package, I'm pretty sure that'd be for legacy/unmaintained projects, not for active projects that just need to be rebuilt against the new openssl.

pieterv · 2017-04-24 14:06:43

Scimmia wrote:

Update again, maybe trying a different mirror
When i manually symlink /usr/lib/libssl.so.1.0.0 to /usr/lib/libssl.so.1.1it works. I need to symlink als libcrypto.so.1.1 in a similar way. This is of course a temporary fix.
Not a fix at all, a horrible, horrible hack that could screw up countless things. Don't post shit like that on the forums.

I said it was a _temporary fix_. Not a fix at all indeed. And I wouldn't call that shit. It's called making your system boot again.

Last edited by pieterv (2017-04-24 14:09:22)

Trilby · 2017-04-24 14:09:22

Pieterv, if you think Scimmia was to abrupt, you could suggest that - however he is completely correct. Your proposed solution is a very bad idea. To prevent others from following that advice, flagging it as problematic is worthwhile.

pieterv · 2017-04-24 14:14:22

Trilby wrote:

Pieterv, if you think Scimmia was to abrupt, you could suggest that - however he is completely correct. Your proposed solution is a very bad idea. To prevent others from following that advice, flagging it as problematic is worthwhile.

I never called it a "proposed solution", but never mind, I edited my message.

acottrell · 2017-04-24 14:14:24

doskoi wrote:

There is also the new openssl-1.0 package.

Yes, that just arrived (out of sync with the previous update). It fixes gnuplot (which is apparently not yet rebuilt
to use libssl.so.1.1).

Last edited by acottrell (2017-04-24 14:16:21)

pieterv · 2017-04-24 14:20:51

Trilby wrote:

but most problems are likely due to mirrors that synced while the main repos were in a unclean transition state (some packages pushed, others not).

Okay works now again, after updateing. I must have been caught in the middle of something somehow.

colinkeenan · 2017-04-24 22:55:33

I had the same problem and upgrading from many different mirrors did not solve the problem. I had to install openssl-1.0 as suggested by doskoi. There is some part of plasma workspace or desktop needs to be repackaged.

Trilby · 2017-04-24 22:58:47

colinkeenan wrote:

There is some part of plasma workspace or desktop needs to be repackaged.

Don't keep us in suspense. Tell us which package it is, and file a bug report.

It would seem that none of the plasma packages (or at least none with plasma in the name) have been rebuilt for the openssl update. So whichever ones depend on that should be reported.

I don't use plasma, so I can't check which packages depend on openssl as easily as you can.

colinkeenan · 2017-04-24 23:25:34

I think it's qt5-base which I see has been updated to depend on openssl-1.0. I don't know why I had to install openssl-1.0 manually more than an hour after I upgraded qt5-base.

Trilby · 2017-04-24 23:58:05

Ah, it's likely that you did get an "old" version of qt5-base along with the new openssl. This is a very similar situation as all the other errors today. But in this case, qt5-base was never rebuilt against the new openssl, instead the maintainer seems to have just added the openssl-1.0 dependency and pushed a new pkgrel including that to the repos.

If you had updated after this workaround was pushed to the repos pacman would have pulled in the new dependency, but you happened to have a mirror that was synced after the openssl upgrade but before the dependency on qt5-base was changed.

Batou · 2017-04-25 17:05:48

I'll just chime in as well... after I upgraded, none of the Qt5 apps would work. They all complained about libssl.so.1.0.0 missing. Reinstalling and recompiling apps didn't help either. The only solution that worked was to install openssl-1.0 package as suggested above by doskoi.

I guess we'll have to wait for Qt5 to be updated for a real fix?

Scimmia · 2017-04-25 17:08:17

It's already been updated, and for a long time. Either your mirror sucks or you aren't using the packages in Extra.

loqs · 2017-04-25 17:29:25

Scimmia wrote:

It's already been updated, and for a long time. Either your mirror sucks or you aren't using the packages in Extra.

https://www.archlinux.org/packages/extr … /qt5-base/

Signature Date: 2017-04-13 14:58 UTC
Last Updated: 2017-04-24 12:10 UTC

Scimmia are you referring to some other package than qt5-base-5.8.0-10 which I believe was moved to extra on the Last Updated Date above when you wrote "for a long time"?

Batou · 2017-04-25 17:31:54

Scimmia,

Here's my version info:

Name            : qt5-base
Version         : 5.8.0-10
Build Date      : Thu 13 Apr 2017 10:41:03 AM EDT
Install Date    : Tue 25 Apr 2017 12:18:47 PM EDT

and for example, the app that won't work without libssl.so.1.0.0:

 Name            : qbittorrent
Version         : 3.3.11-1
Build Date      : Fri 10 Mar 2017 12:02:41 PM EST
Install Date    : Tue 25 Apr 2017 12:38:18 PM EDT

I noticed that a new version of qt5-base (5.8.0-11) is in a Staging repo... I think that's what you probably run.

Last edited by Batou (2017-04-25 17:32:38)

Scimmia · 2017-04-25 17:34:18

loqs wrote:

Scimmia wrote:
It's already been updated, and for a long time. Either your mirror sucks or you aren't using the packages in Extra.
https://www.archlinux.org/packages/extr … /qt5-base/
Signature Date: 2017-04-13 14:58 UTC
Last Updated: 2017-04-24 12:10 UTC
Scimmia are you referring to some other package than qt5-base-5.8.0-10 which I believe was moved to extra on the Last Updated Date above when you wrote "for a long time"?

In this case, I'm classifying more than 28 hours as a long time. If your mirror is that far behind, it's not worth much.

Scimmia · 2017-04-25 17:35:44

Batou wrote:

Scimmia,
Here's my version info:
Name            : qt5-base
Version         : 5.8.0-10
Build Date      : Thu 13 Apr 2017 10:41:03 AM EDT
Install Date    : Tue 25 Apr 2017 12:18:47 PM EDT
 
and for example, the app that won't work without libssl.so.1.0.0

Of course it won't which is why it has a hard dep on openssl-1.0 and should require no intervention on the part of the user at all.

Batou · 2017-04-25 17:41:51

Scimmia,
I don't see that dependency on my system.

Name            : qbittorrent
Version         : 3.3.11-1
Depends On      : libtorrent-rasterbar  qt5-base  desktop-file-utils  hicolor-icon-theme  xdg-utils

Maybe that should be added by a maintainer...

Scimmia · 2017-04-25 17:43:22

I never said a word about qbittorrent.

loqs · 2017-04-25 17:44:37

@Scimmia thank you for the response in that context it makes much more sense to me.

Batou · 2017-04-25 17:56:33

Ah, I found the dependency in qt5-base. Thanks for clarifying it!

Strangely enough, after I upgraded everything, openssl-1.0 was supposedly installed however there was no libssl.so.1.0.0 present. pacman also reported openssl-1.0 as installed. Only after I manually reinstalled openssl-1.0 did libssl.so.1.0.0 come back. I'm suspecting some other package removed it. Maybe openssl-1.1? Anyway, glad this was all cleared up. Thanks!!

Arch Linux

#1 2017-04-24 13:38:22

[solved] KDE5 Plasma missing libssl.so.1.0.0

#2 2017-04-24 13:41:30

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#3 2017-04-24 13:45:39

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#4 2017-04-24 13:48:55

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#5 2017-04-24 13:51:32

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#6 2017-04-24 13:55:03

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#7 2017-04-24 14:06:43

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#8 2017-04-24 14:09:22

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#9 2017-04-24 14:14:22

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#10 2017-04-24 14:14:24

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#11 2017-04-24 14:20:51

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#12 2017-04-24 22:55:33

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#13 2017-04-24 22:58:47

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#14 2017-04-24 23:25:34

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#15 2017-04-24 23:58:05

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#16 2017-04-25 17:05:48

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#17 2017-04-25 17:08:17

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#18 2017-04-25 17:29:25

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#19 2017-04-25 17:31:54

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#20 2017-04-25 17:34:18

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#21 2017-04-25 17:35:44

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#22 2017-04-25 17:41:51

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#23 2017-04-25 17:43:22

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#24 2017-04-25 17:44:37

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

#25 2017-04-25 17:56:33

Re: [solved] KDE5 Plasma missing libssl.so.1.0.0

Board footer