Update error for pacman -Syu

[chucha]

Hallo! The problem - no update now.
The result -
Preformatted text(227/227) checking package integrity ----] 100%
error: a52dec: signature from “Balló György bgyorgy@archlinux.org” is unknown trust
:: File /var/cache/pacman/pkg/a52dec-0.8.0-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: libx11: signature from “Andreas Radke andyrtr@archlinux.org” is unknown trust
:: File /var/cache/pacman/pkg/libx11-1.8.5-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).Preformatted text
Then I have made:
sudo pacman-key --init
sudo pacman-key --populate
vlad@dh370 ~]$ sudo pacman-key --init
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from ‘/etc/pacman.d/gnupg/secring.gpg’ to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key…
gpg: directory ‘/etc/pacman.d/gnupg/openpgp-revocs.d’ created
gpg: revocation certificate stored as ‘/etc/pacman.d/gnupg/openpgp-revocs.d/A730B6A1B4AE18F8B731AA32133483B42E1978E0.rev’
gpg: Done
==> Updating trust database…
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
[vlad@dh370 ~]$ sudo pacman -S archlinux-keyring
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you’re sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
[vlad@dh370 ~]$ sudo rm /var/lib/pacman/db.lck
[sudo] password for vlad:
rm: cannot remove ‘/var/lib/pacman/db.lck’: No such file or directory
[vlad@dh370 ~]$ sudo pacman -S archlinux-keyring
warning: archlinux-keyring-20230504-1 is up to date – reinstalling
resolving dependencies…
looking for conflicting packages…

Package (1) Old Version New Version Net Change

core/archlinux-keyring 20230504-1 20230504-1 0,00 MiB

Total Installed Size: 1,61 MiB
Net Upgrade Size: 0,00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [----------------------] 100%
downloading required keys…
:: Import PGP key 6D42BDD116E0068F, “Christian Hesse eworm@archlinux.org”? [Y/n] y
(1/1) checking package integrity [----------------------] 100%
error: archlinux-keyring: signature from “Christian Hesse eworm@archlinux.org” is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20230504-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.
´´´´´´´´´´´´´´´´´´´´´´´´´´
And now I do not know what must one do.
I’d like help,
Thanks.

[chikenf00t]

might want to take a look at this thread:

[FAQ] Issues with “signature is marginal trust”, "signature is unknown trust", or “invalid or corrupted package”

If you’re getting an error similar to “Can’t update: signature from *** is marginal trust” or “invalid or corrupted package” you probably just need to update your package signing keys: sudo pacman -Sy archlinux-keyring endeavouros-keyring sudo pacman -Syu Also make sure your system clock is correct! Of course, it’s also possible that the package file actually is corrupt. Remove it from /var/cache/pacman/pkg/ so pacman will download it again. If no package file is explicitly mentioned then yo…

[chucha]

Thank you.

1. [vlad@dh370 ~]$ sudo pacman -Sy archlinux-keyring endeavouros-keyring
   [sudo] password for vlad:
   :: Synchronizing package databases…
   error: failed to synchronize all databases (unable to lock database)
   [vlad@dh370 ~]$
2. System clok is OK.
3. Must I fuethemore remove /var/cache/pacman/pkg/ ?

[chikenf00t]

Sure, give that next step a try.

[chucha]

It seems, does not work…
Preformatted text[vlad@dh370 ~]$ sudo rm -r /var/cache/pacman/pkg/
[sudo] password for vlad:
[vlad@dh370 ~]$ sudo pacman -Sy archlinux-keyring endeavouros-keyring
:: Synchronizing package databases…
error: failed to synchronize all databases (unable to lock database)
[vlad@dh370 ~]$

[chikenf00t]

Take a look at this also, it looks like this new error. “Failed to init transaction (unable to lock database)” error

[dalto]

@chucha

sudo rm -r /var/cache/pacman/pkg/

Why would you delete your package cache in this situation? Those are the backups of all your packages.

@chucha

error: failed to synchronize all databases (unable to lock database)

Since you are getting this error and not having a db.lck file, it probably means you have some process or something else locking your pacman database.

[chucha]

Hmmm…
So, PC shutdow, … sorry, did new start.
Then the first step:
[vlad@dh370 ~]$ sudo pacman -Syu
[sudo] password for vlad:
:: Synchronizing package databases…
error: failed to synchronize all databases (unable to lock database)
[vlad@dh370 ~]$
It is pity, no idea…

[dalto]

Try: sudo rm /var/lib/pacman/db.lck first?

[chucha]

Made 2 hours ago, but again -
vlad@dh370 ~]$ sudo rm /var/lib/pacman/db.lck
[sudo] password for vlad:
rm: cannot remove ‘/var/lib/pacman/db.lck’: No such file or directory
[vlad@dh370 ~]$

[chikenf00t]

So looking at :: File /var/cache/pacman/pkg/archlinux-keyring-20230504-1-any.pkg.tar.zst is corrupted

and it makes me think maybe you could try resetting all the keys?
https://wiki.archlinux.org/title/Pacman/Package_signing#Resetting_all_the_keys

[chucha]

Yes, with pkill gpg-agent no error failed to synchronize all databases (unable to lock database).
Process begonnen -
sudo pacman -Syu
:: Synchronizing package databases…
endeavouros is up to date
core is up to date
extra 8,3 MiB 9,18 MiB/s 00:01 [----------------------] 100%
community is up to date
multilib is up to date
:: Starting full system upgrade…
resolving dependencies…
looking for conflicting packages…

xfsprogs-6.3.0-1 xorg-xrdb-1.2.2-1 xorgproto-2023.1-1
xterm-382-1 yad-13.0-1.1 yay-12.0.5-1 zbar-0.23.90-3
zeromq-4.3.4-4

Total Download Size: 1361,55 MiB
Total Installed Size: 4425,96 MiB
Net Upgrade Size: 21,22 MiB

:: Proceed with installation? [Y/n] y
warning: no /var/cache/pacman/pkg/ cache exists, creating…
:: Retrieving packages…
chromium-114.0.5… 90,0 MiB 2,46 MiB/s 00:37 [----------------------] 100%
vivaldi-6.1.3035… 100,7 MiB 2,56 MiB/s 00:39 [----------------------] 100%
opera-99.0.4788… 103,4 MiB 2,48 MiB/s 00:42 [----------------------] 100%
libreoffice-fres… 149,8 MiB 2,61 MiB/s 00:57 [----------------------] 100%
linux-6.3.6.arch… 146,6 MiB 2,52 MiB/s 00:58 [----------------------] 100%

BUT then once again -
error: eos-rankmirrors: signature from “manuel manuel@endeavouros.com” is unknown trust
:: File /var/cache/pacman/pkg/eos-rankmirrors-2.14-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: welcome: signature from “manuel manuel@endeavouros.com” is unknown trust
:: File /var/cache/pacman/pkg/welcome-3.64-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: yay: signature from “manuel manuel@endeavouros.com” is unknown trust
:: File /var/cache/pacman/pkg/yay-12.0.5-1-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.
[vlad@dh370 ~]$

Na…, wonderfull !!!

[chikenf00t]

I think this is good news so far now do:

sudo pacman -Sy endeavouros-keyring
sudo pacman -Syu

[fbodymechanic]

If you could format this so we can read it as a terminal, that would be great. It’s in the welcome post.

[chucha]

Mmm…
A miracle happens and (or) you are a genius !!!
System is working !!??!
VERY THANK YOU VERY MUCH.

[fbodymechanic]

@chucha

community is up to date

You will also want to merge your pacnew files. . .

[chikenf00t]

Glad we were able to get this running for you. Please mark whichever post fixed this for you as an answer. On the other hand, what @fbodymechanic is suggesting may also be a good idea.

[chucha]

OK, I see, thanks