Difficulty Installing Exodus and a Malfunctioning Pacman

junk_f00d · 2017-06-14 18:40:45

Hello, I just learned of AUR and used PKGBUILD to install Exodus. The build procedure terminated with:

Installing package exodus with pacman -U...
/usr/bin/pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
==> WARNING: Failed to install built package(s).

And now when I try launch Exodus I am fed the same libcrypto message, and pacman doesn't work for the same reason.

Reading around, https://bbs.archlinux.org/viewtopic.php?id=225478 I've heard a whole system update is supposed to fix, but I'm not sure how to patch pacman to allow that to happen. In many other threads I viewed, it seemed it was a problem of the library being linked incorrectly, but I'm unsure how to approach fixing that, or if that is even the cause.

Slithery · 2017-06-14 18:43:50

Post #28 in the linked thread tells you how to fix pacman. What happened when you tried?

junk_f00d · 2017-06-14 18:53:05

slithery wrote:

Post #28 in the linked thread tells you how to fix pacman. What happened when you tried?

Didn't see that until now, but let me be clear about a couple things first:

The link leads to this page: https://wiki.archlinux.org/index.php/Pa … an_upgrade, where it describes "the case that pacman crashes with a "database write" error while removing packages, and reinstalling or upgrading packages fails thereafter", and I don't believe this has been my case yet; do you believe the instructions would still apply?

As an example:
sudo pacman -S vlc
pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

I ask because in the other threads I saw (usually involving openssl for some reason) the user had to copy some file to the proper location. which seems like it might be the case given how similar my error messages were to theirs.

At any rate, thank you for your time and generosity!

Slithery · 2017-06-14 18:59:13

I agree, the name is slightly misleading but yes, those are the instructions you are looking for.

The other fixes in the openssl threads will work as well, they are both just different methods of achieving the same outcome - bringing your system to a fully updated state when pacman isn't working.
The only difference is the wiki link is more generalised, and will work in more situations.

Last edited by Slithery (2017-06-14 19:03:39)

jasonwryan · 2017-06-14 19:08:04

How did you install Arch?

junk_f00d · 2017-06-14 19:08:38

slithery wrote:

I agree, the name is slightly misleading but yes, those are the instructions you are looking for.
The other fixes in the openssl threads will work as well, they are both just different methods of achieving the same outcome - bringing your system to a fully updated state when pacman isn't working.
The only difference is the wiki link is more generalised, and will work in more situations.

Ahh ok, thank you! I'll update with how it goes :-) it's gonna take a bit for me to prepare installation media

junk_f00d · 2017-06-14 20:36:32

jasonwryan wrote:

How did you install Arch?

I'm not sure I know how to answer that in a helpful way, but I installed it via USB, if that's what you're asking..

slithery wrote:

I agree, the name is slightly misleading but yes, those are the instructions you are looking for.
The other fixes in the openssl threads will work as well, they are both just different methods of achieving the same outcome - bringing your system to a fully updated state when pacman isn't working.
The only difference is the wiki link is more generalised, and will work in more situations.

Ok, after booting from media I had some confusion. My shell was zsh for some reason, wouldn't change to bash, and the instructions on the wiki were incompatible. Working on this now.. Ahh! I had the wrong filesystem as root I guess.... Don't know why I have an unused 15G paritition at /dev/sda3 (..probably for a shared drive with my windows dual boot that I forgot about..), and my root is /dev/sda6 with 149G, but ok, gonna try again

Ok, as an update this didn't fix it (yet). I was unable to complete the instructions because I'm still stuck in zsh shell while the instructions must be bash (I could be completely wrong about this though) and getting a parse error near '}', despite running csch -s /bin/bash after finding it's location using csch -l. So currently stuck, and may have to abondon this fix for today as it's taking a large chunk of it, but I will monitor this thread and attempt fixes and leave feedback whenever suggestions are left :-) Perhaps at this point that other solution I was finding in those other threads may be of more use, but I'm not sure where I would need to placing my library, or how to find more info on that.

Last edited by junk_f00d (2017-06-14 20:46:19)

seth · 2017-06-15 07:32:00

My shell was zsh for some reason, wouldn't change to bash, and the instructions on the wiki were incompatible.

despite running csch -s /bin/bash after finding it's location using csch -l

Which Archlinux distribution do you use? (ie. manjaro, blackarch, ...)

Arch Linux

#1 2017-06-14 18:40:45

Difficulty Installing Exodus and a Malfunctioning Pacman

#2 2017-06-14 18:43:50

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#3 2017-06-14 18:53:05

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#4 2017-06-14 18:59:13

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#5 2017-06-14 19:08:04

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#6 2017-06-14 19:08:38

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#7 2017-06-14 20:36:32

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

#8 2017-06-15 07:32:00

Re: Difficulty Installing Exodus and a Malfunctioning Pacman

Board footer