Pamac crashes

I installed pamac and it has been working fine for about a month and then a new update installed tonight and it crashes . when I launch it with a terminal I get “ (pamac-manager:10380): GLib-ERROR **: 22:10:36.425: ../glib/glib/gmem.c:106: failed to allocate 5 bytes
Aborted (core dumped) pamac-manager

So I have no idea how to fix this I tried to reinstall using pakman but Pakman does not seem to find any files to install , any ideas ?

pamac wont install with pacman it is only in the aur you would need to use a aur helper like yay to install. so something like yay -S pamac-aur

I’m more echoing what @theremper has already suggested, but offering some extra clarification.

pacman can be used when installing packages from the official Arch repositories. On EndeavourOS, the default official repositories include:

  • endeavouros
  • core
  • extra
  • multilib

You can browse most of these (with the exception of endeavouros) here:

When installing packages from the AUR, you’ll need a helper (if you don’t want to do it manually using makepkg). EndeavourOS by default comes with yay, which @theremper noted.

  • pacman: Can be used for official packages only.
  • yay: Can be used for official packages and AUR packages.

So you can use yay instead of pacman, when installing official Arch packages, using a near identical syntax.

To install:

yay -Syu somepackage

To remove:

yay -R somepackage

To remove orphan packages (leftover dependencies with no packages depending on them anymore):

yay -Yc

nothing in any of these kind replies is of any real help but I do appreciate the effort :slight_smile:

If I try to reinstall using Yay ,or uninstall using Yay it does not work . When i try uninstalling using Yay says package not found . I am at a loss on how to repair the issue . Guess my only recorse is wipe and reinstall . :frowning:

Information is really important.

When you try to install it (pamac?), can you please copy and paste the resulting output.

When I do a search for pamac withyay pamac I will get this result.

14 aur/libpamac-flatpak 1:11.7.4.3.gc7efe92-1 (+3 0.00) 
    Pamac package manager library based on libalpm. With Flatpak support
13 aur/libpamac-full 1:11.7.4.3.gc7efe92-1 (+15 0.09) 
    Library for Pamac package manager based on libalpm - flatpak and snap support enabled
12 aur/pamac-tray-plasma-git r21.58353a1-2 (+2 0.00) 
    Pamac tray icon for Plasma
11 aur/libpamac-aur 11.7.4-2 (+51 1.19) 
    Pamac package manager library based on libalpm
10 aur/pamac-flatpak 11.7.4-1 (+6 0.18) 
    A GUI frontend for libalpm. With Flatpak support
9 aur/pamac-tray-icon-plasma 0.1.4-1 (+23 0.06) 
    Pamac tray icon for plasma users
8 aur/pamac-git 11.7.3.r3.gf756a05-1 (+1 0.00) 
    Pamac package manager - library, gui, cli
7 aur/pamac-aur-git 11.7.3.r3.gf756a05-1 (+29 0.04) 
    Pamac package manager - library, gui, cli
6 aur/pamac-classic-fixed 7.3.0.r764.g76e060f-1 (+1 0.49) 
    A Gtk3 frontend for libalpm - classic version - AUR not working
5 aur/pamac-cli 11.7.4-1 (+17 0.87) 
    Pamac cli frontend for libalpm
4 aur/pamac-gtk3 10.6.0+2+g036cf36d-1 (+2 0.00) 
    A Package Manager based on libalpm with AUR and Appstream support (GTK3)
3 aur/pamac-all 11.7.4-1 (+46 0.32) 
    A GUI frontend for libalpm (everything in one package - snap, flatpak, appindicator, aur, appstream)
2 aur/pamac-classic 7.3.0-5 (+16 0.00) 
    A Gtk3 frontend for libalpm - classic version
1 aur/pamac-aur 11.7.4-2 (+412 2.05) 

So if you would do the same behind one of this packages there should be something like (installed).

Don’t bother to wipe. Pamac does this occasionally. It will be fixed – eventually. Pamac is actually part of Manjaro, and they tend to be a couple of weeks behind Arch in their updates, so probably haven’t discovered it yet.

I got the same error about an hour ago. Sadly, we’ll have to make do with command-line tools in the interim.

ok here is what I get

yay -R pamac
[sudo] password for brothergc:
error: target not found: pamac
→ exit status 1

Before uninstalling, you can check what you have installed exactly, so you can ensure you’re uninstalling the right thing:

yay -Q | grep pamac

Or as @keescase noted with his example of yay pamac, the installed one will be shown as “installed” (or something like that).

yay -Q | grep pamac
libpamac-aur 11.7.4-2
pamac-aur 11.7.4-2

The appropriate command then, is:

yay -R pamac-aur

But do note what @grenouille mentioned!

ok yay -R pamac-aur worked ! Thanks !! :smile: now to reinstall , lets see how bad I can mess this up LOL ( kidding)

Don’t forget to remove libpamac-aur and pamac-cli before reinstalling, in case it’s one of those components messing things up. All three will be reinstalled with pamac-aur.

After uninstalling a package using yay -R somepackage, remember to run this to clean up orphans:

yay -Yc

(this will likely perform what @grenouille mentioned above)

It is possible to uninstall in a way that removes dependencies (yay -Rcns somepackage), but that can sometimes cause issues with other packages. The above approach is generally safer in my experience.

ok thanks to all ! I appreciate the help . I see that their are 2 versions of Pamac , pamac-aur and paman-git is one better then the other ?

pamac-git pulls from the latest version of the source and builds it on your computer.

That may resolve this issue, but you should note that -git version of packages are typically “pre-release”. So it may introduce bugs.

You’ll also need to update it manually from now on, with either:

yay -S pamac-git

Or blanket updating all devel packages with:

yay --devel

pamac-git is quite a lot older. There is also pamac-all which is a little bit older than pamac-aur.

It would be the latest version. Ignore the version listed in the AUR, as that simply reflects the version when the PKGBUILD was last updated, which the maintainer doesn’t need to do, so long as the recipe remains unchanged.

If you build it now, you will be building from the latest commit, as of right now.

Ah. TIL. Thanks @Bink

A hardy thank you to all who helped

but after trying both versions neither will launch , must be some conflict with same file after the latest update when this nightmare began . Both versions did install and uninstall correctly thanks to the help here and I did remove the orphans before attempting reinstall so for now I am throwing in the towel . Thanks again !