Pamac seems to be a bit broken

i get a notification of 4 available updates,the tray icon turns red.
when trying to open Pamac it is stuck at:“checking for updates 90%” and i have to force close it.

running sudo pacman -Syu in terminal clears it; no available updates,icon turn white again,and i’m able to open Pamac.

this happened twice.

Have you tried pamac upgrade in the terminal to see what it is doing or if it works ok.

no,next time i might try.
it might be related to this?:

How long you waited?

I recommend to refresh your Mirrors and try it again, possible a server isn’t reach able and you have to wait for a timeout:

sudo pacman-mirrors --fasttrack

Sometimes, the last 90% are checks for AUR. The downloaded AUR database is in JSON and the decoding takes a very long time and memory.

What happens if you do this in the terminal?

(pamac update)

As told in the other topic, disable flatpak and aur updates in pamac. Only after a core system update with pamac gui or sudo pacman -Syu you can flatpak update and yay -Sua

3 Likes

i just re-chose my mirrors,disabled AUR support(i currently don’t use Flatpak),ran
sudo pacman -Syu and re-enabled it.

there are no available updates,same with pamac update.

i can access Pamac and refresh the database from there with no issues,
it’s just when i get those supposedly 4 updates,that it gets stuck.

it doesn’t seem like a big issue,just weird.

Maybe packages-meta-ext-v1.json.gz in /var/tmp/pamac/dbs/sync/ is corrupt? Have you tried deleting that file? Pamac should recreate it upon opening if you have AUR support enabled.

i don’t have anything with this name there

there are no available updates,same with pamac update.

Try updating AUR packages

pamac update --aur
1 Like

Nothing to do.
no updates.

Having AUR enabled in the GUI may cause strange behaviour.

  1. Disable AUR update checking

I also would look in pamac under Foreign and remove AUR Orphans there which additional highlighted marked with AUR

i have these,but i’m using them:

and no orphans:

It would be usefull if you can tell us what your last changes was… more background story, when was your last update and did everything working after it?

Didn’t you update for a longer time and missed a few stable release updates?

What are the pacman.log showing, since the last bigger stable update?

/var/log/pacman.log

TBH, your orphans and foreign list looks a little bid to clean… i hope you didnt had something removed which was important.

If i had cleaned my whole orphans/foreign my Manjaro would be broken :sweat_smile:

No, it wouldn’t. Orphans are not needed for anything. AUR is optional.
In fact, cleaning orphans is part of the maintanance and prevents future problems.

Orphans can end up being desirable.

Think of a scenario where a use had installed a number of packages and managed to get ‘important package X’ as a dependency. Then the user removes the other packages that would have required ‘important package X’, but the user still desires to retain that package.

This is just one example.

But such situations also call for the user to take action.

If you have an orphan you would like to keep … make it not an orphan by marking it as explicitly installed.

ex:

pacman -Qdtq

And firefox is an orphan, but you wish to keep it.

sudo pacman -D --asexplicit firefox

Now pacman -Qdtq wont list firefox.

2 Likes

Screenshot of Foreign packages shows vmware-workstation from AUR
but skypeforlinux-stable-bin is no longer available from AUR

[2024-03-30T11:48:49+0000] [ALPM] removed skypeforlinux-stable-bin (8.109.0.209-1)
[2024-03-30T11:48:50+0000] [ALPM] installed skypeforlinux-bin (8.115.0.217-1)

I suggest build AUR package skypeforlinux-bin 8.130.0.205-1

1 Like

I really wished that would be easy like that, but its not.

I have ton of orphans in my system, that are important…

:point_up: My Steam was on of this Orphans that i had to marking it as explicitly installed.

sof-firmware is also needed as far as i know for my Creative Soundblaster AE-5 card but it listed under orphans.

And there is many many more stuff, where im not sure if i can blindly delete it, if i run into trouble after the next boot.

And to you check little file is really time consuming :frowning:

Well, if you think something might be important, just mark it as explicitly installed.