Pacman not functioning literally no output

I have absolutely zero clue why this is happening its very odd. When trying to use pacman I get zero output I can't build or delete anything I can't even update my mirrors. In addition yay is not functioning either but it at least is giving me an error. " yay: error while loading shared libraries: /usr/lib/libalpm.so.12: file too short"

Sounds like the file is corrupt.

I would download pacman-static like this:

wget https://pkgbuild.com/~eschwartz/repo/x86_64-extracted/pacman-static

Then make it executable and use pacman-static to reinstall pacman

chmod a+x ./pacman-static
sudo ./pacman-static -S pacman

Yeah looks like some files is corrupted but it's not letting me run that.
"""pacman-5.2.1-7-x86_64 868.3 KiB 1497 KiB/s 00:01 [##################################] 100%
(1/1) checking keys in keyring [##################################] 100%
(1/1) checking package integrity [##################################] 100%
error: pacman: signature from "Philip Müller (Called Little) philm@manjaro.org" is unknown trust
:: File /var/cache/pacman/pkg/pacman-5.2.1-7-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
"""
should i just try to use --force?

Try this:

sudo ./pacman-static -Sy archlinux-keyring manjaro-keyring
sudo pacman-key --populate archlinux manjaro
sudo pacman-key --refresh-keys
sudo ./pacman-static -Syu pacman

""":: Proceed with installation? [Y/n] y
:: Retrieving packages...
archlinux-keyring-20200422-1-any 890.6 KiB 1536 KiB/s 00:01 [##################################] 100%
manjaro-keyring-20200603-1-any 131.0 KiB 18.3 MiB/s 00:00 [##################################] 100%
(2/2) checking keys in keyring [##################################] 100%
(2/2) checking package integrity [##################################] 100%
error: archlinux-keyring: signature from "Christian Hesse (Arch Linux Package Signing) arch@eworm.de" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20200422-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: manjaro-keyring: signature from "Philip Müller (Called Little) philm@manjaro.org" is unknown trust
:: File /var/cache/pacman/pkg/manjaro-keyring-20200603-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded."""
No luck :confused: Same thing corrupted packages

So i got past the pgp issue but now I have a new problem:
"""
error: failed to commit transaction (conflicting files)
pacman: /usr/bin/checkupdates exists in filesystem
pacman: /usr/bin/makepkg exists in filesystem
pacman: /usr/bin/makepkg-template exists in filesystem
pacman: /usr/bin/paccache exists in filesystem
.....
pacman: /usr/share/pkgconfig/libmakepkg.pc exists in filesystem
pacman: /usr/share/vim/vimfiles/ftdetect/PKGBUILD.vim exists in filesystem
pacman: /usr/share/vim/vimfiles/ftplugin/PKGBUILD.vim exists in filesystem
pacman: /usr/share/vim/vimfiles/syntax/PKGBUILD.vim exists in filesystem
pacman: /usr/share/zsh/site-functions/_pacman exists in filesystem
Errors occurred, no packages were upgraded."""

You have some pretty significant issues with your system and pacman database. Once you get everything back, I would check on the status of your hard disk.

For now, try this:

sudo ./pacman-static -Syu pacman --overwrite "*"
2 Likes

That did it!! Thank you, I was trying overwrite but i was using a specific file path not just *.
The issue might stem from reverting to an old backup recently due to removing some orphaned packages destroying my lightdm but I can't be sure

1 Like

Does pacman work now?

Yes completely even the add/remove software works. Also it fixed yay for me as well

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by