Libpamac-flatpak stopped working and has a missing lib Arm64

ARM
1

Hey guys I just want to report that libpamac-flatpak stopped working and there is a lib issue with libpamac-flatpak on Arm64 which causes the package to fail to install

Resolving dependencies...
Checking inter-conflicts...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Reinstalling libpamac-flatpak-plugin (11.7.3-4)...
flatpak: error while loading shared libraries: libgpgme.so.11: cannot open shared object file: No such file or directory
Error while configuring libpamac-flatpak-plugin
Error: libpamac-flatpak-plugin: command failed to execute correctly
Transaction successfully finished.

I have gpgme and 2.0.0-1 installed

I was able to temporarily workaround and fix this by doing sudo ln -s /usr/lib/libgpgme.so /usr/lib/libgpgme.so.11 but the package will need to be updated to fix this.

2

hmm after a reboot, removing the symlink I made and testing the package again by reinstalling it now it isn’t complaining about it

So weird, any ideas what happened? :thinking:

3

pacman has been rebuilt using gpgme 2.0 - and pamac uses libalpm, which is pacman’s backend.

Your issue is possibly a cascading dependency issue as flatpak depends on gpgme as well.

The correct approach is to remove the packages where dependency cannot be resolved correct, then after a succesful sync add the packages back.

4

Ahh I see, thanks for the update and letting me know :slight_smile:

6

The issue is the removal of libgpgme.so.11 with the latest updates a couple days ago. Flatpak was also reliant on that but today’s flatpak update resolved the issue for flatpak however, there are still packages reliant on libgpgme.so.11 which is no longer available. One of those packages is “udisks2” which is quite important. I can’t see my attached drives and root partition anymore without it.

By the way, you removed my post because of the symlink suggestion, but the post above mine clearly suggest the exact same thing, so why is it still visible?

1 Like
7

Did you install volume_key rebuild @tartanpion provided here. It fixed my usb drive issue after rebooting.

https://forum.manjaro.org/t/arm-unstable-update-2025-06-04-linux-firefox-pipewire-thunderbird/178595/34

8

Yep that did it. Thanks. I wasnt following that thread. Maybe i should.

1 Like
9

That thread is where all of the upgrade problems are being identified.

10

Perhaps because it did not suggest that as the solution, but as something the user tried, then realised it was not a viable solution.

That’s the actual solution.