You are not logged in.

#1 2022-11-20 03:33:13

2kwatts
Member
Registered: 2022-07-24
Posts: 6
Website

libcrypto.so.1.1: cannot open shared object file: No such file or dire

Hello.

So when I run certain commands (including pacman), I get the error "pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory". I tried to update my system and see if that could help, but I get that same error. The last thing I did with pacman was run "sudo pacman -S base-devel capstone python" for a project. I'm not sure what is causing this.

Thanks, ~2kwatts

Offline

#2 2022-11-20 03:48:04

2kwatts
Member
Registered: 2022-07-24
Posts: 6
Website

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

Update: I have since then restarted my system, but when booting it up, it gets a kernel panic and stops.

Offline

#3 2022-11-20 03:48:39

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,694

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

This happened because you did a partial update. If you ever run pacman -Sy or cancel an update, you can't install anything until you finish the update.

At this point, the simplest option is to use an external pacman to update the system. Since you haven't rebooted, pacman-static (see the AUR page for it) may the the way to go. Otherwise boot an install disk and use pacman from there with the --root option.

Online

#4 2022-11-20 04:01:09

2kwatts
Member
Registered: 2022-07-24
Posts: 6
Website

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

I have an install disk booted. How do I go about using pacman there?

Edit: nevermind, the boot image doesn't even show up in BIOS.

Last edited by 2kwatts (2022-11-20 04:12:03)

Offline

#5 2022-11-20 04:14:12

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,168

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

What do you mean it doesn't show up in BIOS? You said you'd booted it ....


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#6 2022-11-20 04:15:04

2kwatts
Member
Registered: 2022-07-24
Posts: 6
Website

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

I was just thinking ahead for when I got it started up.

Offline

#7 2022-11-20 04:20:33

2kwatts
Member
Registered: 2022-07-24
Posts: 6
Website

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

So now the BIOS menu won't even let me use my keyboard/mouse, so there's no chance of fixing anything now really.

Offline

#8 2022-11-20 04:46:38

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,168

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

Try with as few things connected as possible?

Try from cold boot rather than rebooting (or vice-versa, if possible)?

Try a different keyboard and/or mouse?

Check connections?

Try with a newly created install disk?

You've told us absolutely nothing about your system ...


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#9 2022-11-20 05:02:06

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: libcrypto.so.1.1: cannot open shared object file: No such file or dire

Booting to an install disk is exactly the same now as it was when you installed arch linux initially.  Nothing you did in the installed OS could change this process.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

Board footer

Powered by FluxBB