So after
Alkaris still did not that?
I though that we went further, and the getting all of updates is already in the past.
What if your storage has a bad block?
Try to re-install all packages, including pamac (cause pamac has several dependencies of packages) with re-configuring the pamac (case of config files is bad and pamac uses a wrongly read value at some point (that 95%) and than segfauls while trying to use that faulty value):
- Close pamac system tray icon.
- Remove pamac app settings:
rm -rf ~/.config/pamac - Purge cache of downloaded packages:
sudo pacman -Scc(Yeverywhere) - Re-install all packages with
pacman: pacman/Tips and tricks - ArchWiki
$ su
enter root’s password (not your user’s one; that password you already entered at least at the OS installation stage) and than
# pacman -Qqn | pacman -S -
and after
# exit
$
Reboot the PC and re-check the db update via terminal
$ pamac update --force-refresh
if still segfaults, re-initialize other pamac dependencies like re-installation DBs and keys: Update archive corrupted - #10 by linux-aarhus
If you want you can report your case in order to get developers support, if you believe that it is the app problem and not your environment case: Issues · Applications / pamac · GitLab
But all participants/poster of that thread don’t have that issue, otherwise they would tell about that problem too. I think most probably it is your environment issue (other software around pamac or hardware).