FS#53776 - [terminology] error while loading libssl.so.1.0.0: cannot open (since openssl > 1.1.0)

Attached to Project: Arch Linux
Opened by Silvestr Hašek (ETNyx) - Monday, 24 April 2017, 13:22 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 24 April 2017, 14:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
while you try to start terminology
terminology: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

This happened since openssl > 1.1.0

Additional info:
extra/terminology 1.0.0-1
core/openssl 1.1.0.e-1



Steps to reproduce:
Update your machine start terminology
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 24 April 2017, 14:47 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Monday, 24 April 2017, 13:27 GMT
Entire system up to date? What version, specifically, of efl?
Comment by Isaac (isaacwhanson) - Monday, 24 April 2017, 14:07 GMT
this is occurring with multiple packages git, node, atom, ...
because most mirrors do not have packages built against the new openssl-1.1.0.e-1 (build against 1.0.0 in most cases)
Comment by Naoki Kawakami (aya) - Monday, 24 April 2017, 14:14 GMT
# pacman -S openssl-1.0

should fix you

But honestly, there should have been announcement on the top page because so many things broke with openssl update.
Comment by Doug Newgard (Scimmia) - Monday, 24 April 2017, 14:16 GMT
Very litte/nothing broke with the update. There were some serious mirror problems (and some serious user problems) that a full update should fix.
Comment by Naoki Kawakami (aya) - Monday, 24 April 2017, 14:18 GMT
Okay Doug, maybe. But this did not work for me. And I always do entire system update.
Comment by Isaac (isaacwhanson) - Monday, 24 April 2017, 14:24 GMT
I had to try many mirrors before finding one where many (but not all) packages that I use are updated. I always do a full upgrade (don't actually know how to do a partial). had to make symlinks for libs to get upgrading to work after the first full upgrade failed.
Comment by Doug Newgard (Scimmia) - Monday, 24 April 2017, 14:26 GMT
No, you didn't have to make stupid symlinks, you choose to instead of fixing it correctly.
Comment by Isaac (isaacwhanson) - Monday, 24 April 2017, 14:28 GMT
I guess I didn't know how to fix it correctly at the time. always open to learning the correct way. perhaps a post on the site would have been useful. thanks for your help, it is appreciated :)
Comment by Silvestr Hašek (ETNyx) - Monday, 24 April 2017, 14:38 GMT
Sorry i broke my system, even wi-fi didnt start,..
At start I did as wiki recomend:
[2017-04-24 14:56] [PACMAN] Running 'pacman -Syu'

after recovery from broken state
[2017-04-24 16:01] [PACMAN] Running 'pacman -Syu'
[2017-04-24 16:02] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1)
[2017-04-24 16:08] [ALPM] installed openssl-1.0 (1.0.2.k-3)

and its fixed now,...
close issue?

Loading...