- Arch Linux User Repository
- Search Criteria
- Package Details: pamac-aur 10.2.0-2
- Package Actions
- Dependencies (27)
- Required by (5)
- Sources (1)
- Latest Comments
- bassam commented on 2021-10-04 23:28
- Hanabishi commented on 2021-10-01 16:19
- kanehekili commented on 2021-09-30 17:19
- bxabi commented on 2021-09-29 09:39
- Gotit commented on 2021-06-20 18:50
- Zeph commented on 2021-06-14 10:16
- tigr72 commented on 2021-06-14 10:03
- theone77 commented on 2021-06-13 07:08
- marcos.lcog commented on 2021-06-11 20:26
- darklyn3r commented on 2021-06-11 18:57
- Arch Linux
- #1 2020-07-22 11:10:25
- pacman: error while loading shared libraries: libalpm.so.12
- #2 2020-07-22 11:15:57
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #3 2020-07-22 11:18:07
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #4 2020-07-22 11:19:16
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #5 2020-07-22 11:19:59
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #6 2020-07-22 11:20:43
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #7 2020-07-22 11:29:43
- Re: pacman: error while loading shared libraries: libalpm.so.12
- #8 2020-07-22 12:08:35
- Re: pacman: error while loading shared libraries: libalpm.so.12
- How to Fix yay: error while loading shared libraries: libalpm.so.12
- 1 min
- How to fix yay error – while loading shared libraries: libalpm.so.12
- Arch Linux
- #1 2008-08-11 08:07:58
- libalpm.so.2: cannot open shared object file
- #2 2008-08-11 09:09:25
- Re: libalpm.so.2: cannot open shared object file
- #3 2008-08-11 09:12:38
- Re: libalpm.so.2: cannot open shared object file
- #4 2008-08-11 09:24:55
- Re: libalpm.so.2: cannot open shared object file
- #5 2008-08-11 09:29:19
- Re: libalpm.so.2: cannot open shared object file
- Arch Linux
- #1 2019-12-06 02:18:00
- auracle: error while loading shared libraries: libalpm.so.11
- #2 2019-12-06 02:30:52
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #3 2019-12-06 03:50:17
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #4 2019-12-06 05:05:31
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #5 2019-12-06 05:13:10
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #6 2019-12-06 07:20:45
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #7 2021-10-07 11:37:50
- Re: auracle: error while loading shared libraries: libalpm.so.11
- #8 2021-10-07 11:49:40
- Re: auracle: error while loading shared libraries: libalpm.so.11
Arch Linux User Repository
Search Criteria
Package Details: pamac-aur 10.2.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/pamac-aur.git (read-only, click to copy) |
---|---|
Package Base: | pamac-aur |
Description: | A Gtk3 frontend, Package Manager based on libalpm with AUR and Appstream support |
Upstream URL: | https://gitlab.manjaro.org/applications/pamac |
Keywords: | gui installer libalpm package pacman yay |
Licenses: | GPL3 |
Conflicts: | pamac, pamac-tray-appindicator |
Provides: | pamac=10.2.0-2 |
Submitter: | Zeph |
Maintainer: | Zeph |
Last Packager: | Zeph |
Votes: | 347 |
Popularity: | 4.88 |
First Submitted: | 2013-12-05 12:57 |
Last Updated: | 2021-10-03 21:21 |
Dependencies (27)
- archlinux-appstream-data (archlinux-appstream-data-pamac)
- dbus-glib (dbus-glib-git)
- desktop-file-utils (desktop-file-utils-git)
- git (git-git, git-vfs)
- json-glib (json-glib-git)
- libhandy (libhandy-git, libhandy-glade-catalog-disabled-git)
- libnotify (libnotify-gtk2, libnotify-id-git, libnotify-id)
- libsoup (libsoup-gnome-git, libsoup-gnome)
- polkit (polkit-no-script-git, polkit-git, polkit-consolekit, polkit-duktape)
- vte3>=0.38 (vte3-ng-emoji-terminix-zsh-notify, vte3-ng-fullwidth-emoji, vte3-git, vte3-tilix, vte3-ng, vte3-kinetic, vte3-nohang, vte3-selectall, vte3-notification)
- appstream-glib>=0.7.18-1 (appstream-glib-git)
- libpamac-aur>=11.1
- glib2>=2.42 (glib2-clear, glib2-quiet, glib2-selinux, glib2-nodocs-git, glib2-git, glib2-patched-thumbnailer)
- gtk3>=3.22 (gtk3-adwaita-3-32-git, gtk3-git, gtk3-ubuntu, gtk3-no_deadkeys_underline, gtk3-classic, gtk3-patched-filechooser-icon-view, gtk3-typeahead)
- gnutls>=3.4 (gnutls-tiny-git, gnutls-git, gnutls-next, gnutls-openssl, gnutls-nodocs-git)
- asciidoc (asciidoc-git) (make)
- gettext (gettext-git) (make)
- gobject-introspection (gobject-introspection-git) (make)
- itstool(make)
- libappindicator-gtk3 (libappindicator-gtk3-ubuntu, libappindicator-bzr) (make)
- meson (meson-git) (make)
- ninja (ninja-git, ninja-samurai, ninja-mem, ninja-kitware, ninja-bin) (make)
- xorgproto (xorgproto-git) (make)
- vala>=0.46 (vala0.42, vala0.44, vala-git) (make)
- gtk3>=3.22 (gtk3-adwaita-3-32-git, gtk3-git, gtk3-ubuntu, gtk3-no_deadkeys_underline, gtk3-classic, gtk3-patched-filechooser-icon-view, gtk3-typeahead) (make)
- lxsession (lxsession-git) (optional) – needed for authentification in Xfce, LXDE etc.
- polkit-gnome (polkit-gnome-gtk2, xfce-polkit-git, xfce-polkit, polkit-gnome-git) (optional) – needed for authentification in Cinnamon, Gnome
Required by (5)
- bootsplash-manager-bin (requires pamac)
- mintmenu (requires pamac) (optional)
- pamac-tray-icon-plasma (requires pamac)
- pamac-zsh-completions (requires pamac)
- update-notifier (requires pamac) (optional)
Sources (1)
Latest Comments
bassam commented on 2021-10-04 23:28
Getting an error
Hanabishi commented on 2021-10-01 16:19
kanehekili commented on 2021-09-30 17:19
Same problem on Arch linux:
bxabi commented on 2021-09-29 09:39
I’m getting this error:
Gotit commented on 2021-06-20 18:50
@Zeph I tried your fix dated 6/10/21 but can’t remove pamac as I get:
error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory
Had to grab the libalpm.so.12 files from a 5.x version of pacman and drop them in usr/lib. Then I could:
Zeph commented on 2021-06-14 10:16
tigr72 commented on 2021-06-14 10:03
In the settings, the cache size always shows 0 files, 0 bytes and the button for clearing the cache is not active
theone77 commented on 2021-06-13 07:08
Thank you Zeph, I did as you said: yay -Rncs pamac-aur yay -S pamac-aur All good now.
marcos.lcog commented on 2021-06-11 20:26
pamac-alll is working perfectly with libpamac-full!! I just had to remove pamac-aur before getting the new packs.
darklyn3r commented on 2021-06-11 18:57
Thanks @Zeph .. I already removed and reinstalled pacman and now everything works very well for me
Copyright © 2004-2021 aurweb Development Team.
AUR packages are user produced content. Any use of the provided files is at your own risk.
Источник
Arch Linux
You are not logged in.
#1 2020-07-22 11:10:25
pacman: error while loading shared libraries: libalpm.so.12
Hi to everyone. I would like to ask for your help.
I did an system update with pacman -Syu, but i did it while i had hibernation turned on (after few minutes). When i went back to laptop i saw that hibernation turned on, laptop was suspended. I could not bring it again, becasue during update kernel was not replaced corectly. I run Arch-live-usb media, did again update, rebooted and. first thing what i saw was crash. Filesystem was corrupted. I repaired it with fsck, could boot in Arch again but other problem comes.
I cant do upgrade, i cant use pacman because of
Could somebody help or point me? I rebooted, mount root partition into Arch-live-usb. Reinstalled pacman with
Pacman was reinstalled, but when i rebooted to Arch i still have the same problem with libalpm.so.12
So it is in my filesystem. Now i don’t know what to do. Please, help. I cant even check pacman version with
bacuse of this error.
I checked something more
If i think correctly, there is no libalpm.so.12 at all. So, how to force install it, which package have it?
Last edited by firekage (2020-07-22 11:18:08)
#2 2020-07-22 11:15:57
Re: pacman: error while loading shared libraries: libalpm.so.12
There should be more:
from the live ISO.
#3 2020-07-22 11:18:07
Re: pacman: error while loading shared libraries: libalpm.so.12
Essentially you’d need to reinstall pacman.
Not sure how to accompish that.
Maybe you can get the missing files:
(/usr/lib/libalpm.so.12.0.2 belongs to pacman itself) and move them to that directory manually, then try to re-install pacman and fix your system.
edit: too slow. And I already suspected a chroot would be more elegant.
Last edited by ondoho (2020-07-22 11:18:55)
However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.
There’s no objectivity.
#4 2020-07-22 11:19:16
Re: pacman: error while loading shared libraries: libalpm.so.12
There should be more:
from the live ISO.
I did that with arch-usb-live media. Does not work. Still i don’t have this files.
#5 2020-07-22 11:19:59
Re: pacman: error while loading shared libraries: libalpm.so.12
Essentially you’d need to reinstall pacman.
Not sure how to accompish that.
Maybe you can get the missing files:
(/usr/lib/libalpm.so.12.0.2 belongs to pacman itself) and move them to that directory manually, then try to re-install pacman and fix your system.
edit: too slow. And I already suspected a chroot would be more elegant.
Yeah, i figured that, try and did that but still after reinstalling pacman i don’t have this files and cant use it. Unfortunately, in chroot-mode it does not work at all. In chroot-mode i cant install anything because of missing files.
Last edited by firekage (2020-07-22 11:21:23)
#6 2020-07-22 11:20:43
Re: pacman: error while loading shared libraries: libalpm.so.12
Then I refer to @ondoho suggestion.
Extract the respective file from the package archive in the package cache.
But since the file is owned by pacman, this seems rather strange behaviour.
Please provide your full pacman.log and pacman.conf.
There Might be a faulty NoExtract in place.
Last edited by schard (2020-07-22 11:23:26)
#7 2020-07-22 11:29:43
Re: pacman: error while loading shared libraries: libalpm.so.12
When asking questions, provide as much information as possible, including error messages, terminal output, logs, what you have previously tried, what documentation and searches you have attempted, and related configuration files.
However studied and stilted your rant, it can never hide the base and primitve emotion that inspired it.
There’s no objectivity.
#8 2020-07-22 12:08:35
Re: pacman: error while loading shared libraries: libalpm.so.12
When asking questions, provide as much information as possible, including error messages, terminal output, logs, what you have previously tried, what documentation and searches you have attempted, and related configuration files.
I write why. Because of the same missing file libalpm.so.12. Cannot open shared object because of that.
I did something more. I just downloaded missing files, copied it to needed location. Pacman barely works. I can now run commands, but cant update anythig because of «pim-data-exporter», besause conflict files in filesystem. Everything is related to pim-data-exporter, but i don’t know how to completly remove it. Many files, many locations, and doing it manually takes forever.
I don’t know other ways to replace filest that are in filesystem exept do delete it manually — long road, did it. Problem solved but not the way i would like to be.
Last edited by firekage (2020-07-22 13:07:34)
Источник
How to Fix yay: error while loading shared libraries: libalpm.so.12
1 min
This quick guide is to help you to fix yay error – while loading shared libraries: libalpm.so.12.
If you are running Arch Linux in a system for a longer time, things can break due to its rolling release nature combined with your hardware support. If you use the AUR Helper Yay, then sometimes, yay can be corrupted due to several installations, upgrade of other packages.
The YAY helper itself is very stable, but sometimes it gets messed up, and you can not do any installation using it until you fix it. And one of the nagging error is this:
This error particularly comes after upgrading to pacman 6.0 due to incompatibility of shared libraries.
How to fix yay error – while loading shared libraries: libalpm.so.12
- This error can only be fixed by uninstalling yay completely, including its dependencies.
- Then re-installing yay.
- There is no other way to solve this error.
- We already have a guide how to install Yay, however, here are the steps to fix.
- Clone the yay repo from AUR and build. Run the following command in sequence from a terminal window.
After installation, you can try running the command which gave you this error. And you should be all set. If you’re still having error, let me know in the comment box below.
Apparently, this has been encountered by many people and several discussions happened across web. Above is the only solution to this error. And I could not find exact root cause of the problem anywhere except it starts after pacman 6.0 update.
We bring the latest tech, software news and stuff that matters. Stay in touch via Telegram, Twitter, YouTube, and Facebook and never miss an update!
Источник
Arch Linux
You are not logged in.
#1 2008-08-11 08:07:58
libalpm.so.2: cannot open shared object file
Hello, i usually use shaman to install packages so the other day i decided to update my system using it, it asked if i wanted to upgrade pacman first, I said yes. When upgrading pacman finished, shaman did not continue the update so i decided to just shut down the pc. The next day I try to use shaman and it wont launch, when i launch it from terminal i get this:
shaman: error while loading shared libraries: libalpm.so.2: cannot open shared object file: No such file or directory
also, when i try to use yaourt I get:
/usr/bin/pacman-color: error while loading shared libraries: libalpm.so.2: cannot open shared object file: No such file or directory
i deceided to try and pacman -Syu but when it started the update I got the following error:
resolving dependencies.
looking for inter-conflicts.
error: failed to prepare transaction (could not satisfy dependencies)
:: linux-uvc-svn: requires kernel26 Offline
#2 2008-08-11 09:09:25
Re: libalpm.so.2: cannot open shared object file
Both shaman and pacman-color need to be rebuilt against the new libalpm version, which was part of the pacman upgrade.
linux-uvc-svn and virtualbox-modules need to be rebuilt against the 2.6.26 kernel package.
#3 2008-08-11 09:12:38
Re: libalpm.so.2: cannot open shared object file
thanks for your reply but how would i go about doing that?
#4 2008-08-11 09:24:55
Re: libalpm.so.2: cannot open shared object file
For shaman you will have to wait for a new release (scheduled for 1st of Sept from memory). It is not a simple rebuild.
#5 2008-08-11 09:29:19
Re: libalpm.so.2: cannot open shared object file
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Источник
Arch Linux
You are not logged in.
#1 2019-12-06 02:18:00
auracle: error while loading shared libraries: libalpm.so.11
While trying to install AUR packages I’m getting the following error:
Thanks for any help
#2 2019-12-06 02:30:52
Re: auracle: error while loading shared libraries: libalpm.so.11
You need to update/rebuild auracle
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
Online
#3 2019-12-06 03:50:17
Re: auracle: error while loading shared libraries: libalpm.so.11
You need to update/rebuild auracle
I’ve removed auracle however when I got to install auracle from the aur I run
#4 2019-12-06 05:05:31
Re: auracle: error while loading shared libraries: libalpm.so.11
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
Online
#5 2019-12-06 05:13:10
Re: auracle: error while loading shared libraries: libalpm.so.11
#6 2019-12-06 07:20:45
Re: auracle: error while loading shared libraries: libalpm.so.11
It works for me. What if you pass `-C` to makepkg?
#7 2021-10-07 11:37:50
Re: auracle: error while loading shared libraries: libalpm.so.11
While trying to install AUR packages I’m getting the following error:
Thanks for any help
So, did you manage to solve it somehow? I ran into the same issue and rebuilding auracle does not seem to help:
#8 2021-10-07 11:49:40
Re: auracle: error while loading shared libraries: libalpm.so.11
Don’t necrobump a year old thread. Just from the error, make sure base-devel is installed as is mandatory for all AUR PKGBUILDs.
If this is insufficient, open a new thread.
Last edited by V1del (2021-10-07 11:49:58)
Источник