Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"paru: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory" when attempting to run paru #1155

Closed
Bilskirnir3124 opened this issue Mar 17, 2024 · 12 comments

Comments

@Bilskirnir3124
Copy link

Affected Version

paru 2.0.1-1 with pacman 6.1.0-3 running on kernel version 6.7.9-zen1-1-zen.

Description

Attempting to run any command returns the following output.

Output

"paru: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory"

My paru.conf and my pacman.conf

If I can provide any more information please do let me know. I've not used github before this.

@tohsaka888
Copy link

I think the problem is that you upgrade pacman .

You can run this command to check it:

pacman --version

if the result is:

 .--.                  Pacman v6.1.0 - libalpm v14.0.0
/ _.-' .-.  .-.  .-.   Copyright (C) 2006-2024 Pacman Development Team
\  '-. '-'  '-'  '-'   Copyright (C) 2002-2006 Judd Vinet
 '--'
                       This program may be freely redistributed under
                       the terms of the GNU General Public License.

libalpm upgrade to v14.0.0

@Bilskirnir3124
Copy link
Author

Yes. The output matches exactly. I suppose I should just wait until paru upgrades to match?

@tohsaka888
Copy link

Right, i think so.

@Bilskirnir3124
Copy link
Author

Copy. Thank you. I'll go ahead and mark this closed then.

@tohsaka888
Copy link

Hi, @Bilskirnir3124 :

You can try this to fix this problem.

sudo cp /usr/lib/libalpm.so.14 /usr/lib/libalpm.so.13

@Voklen
Copy link

Voklen commented Mar 17, 2024

The latest version of paru seems to work but since it can't find libalpm.so.13 it can't update itself. So we can do that manually.
Go into the directory you originally installed paru in and run

git pull

then

makepkg -si

and this should be fully fixed 😄

Note that if you deleted the directory simply go through the installation again

sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si

@Bilskirnir3124
Copy link
Author

The latest version of paru seems to work but since it can't find libalpm.so.13 it can't update itself. So we can do that manually. Go into the directory you originally installed paru in and run

git pull

then

makepkg -si

and this should be fully fixed 😄

Note that if you deleted the directory simply go through the installation again

git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si

This solved the problem perfectly. Thank you.

@markstos
Copy link

markstos commented Mar 18, 2024

I get an error at the makepkg step:

❯ makepkg -si
==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.

The fix for that is in this related thread: #1149 (comment)

@JJJHolscher
Copy link

Thank you for posting the answer.
Is updating with pacman generally a no-go? I prefer to.

@markstos
Copy link

markstos commented Apr 3, 2024

Is updating with pacman generally a no-go? I prefer to.

Paru is not installed with Pacman: https://github.com/Morganamilo/paru?tab=readme-ov-file#installation It is not in any repo that Pacman knows about.

@JJJHolscher
Copy link

err, I meant
"is updating all my other packages except paru with pacman" generally not recommended when using paru

@markstos
Copy link

markstos commented Apr 3, 2024

It's my understanding that you can safely fix paru and pacman for non-AUR packages. I use paru maximally for simplicity.

One detail that's nice about paru: If pacman needs to run as root and you aren't root, it will just err-out and quit. But if paru needs root, it will prompt you for your sudo password and you can continue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants