Sometimes it also is a db error instead of just an unexpected error. I searched the forums and none of the solutions work.
“Remove db lock” just says “Pacman db lock does not exist!”, “Refresh keyrings” returns some errors:
==> ERROR: The keyring file /usr/share/pacman/keyrings/libgnome.gpg does not exist.
==> ERROR: The keyring file /usr/share/pacman/keyrings/python-proton-linux.gpg does not exist.
==> ERROR: The keyring file /usr/share/pacman/keyrings/python-proton-linux-secretservice.gpg does not exist.
which I think are probably related to AUR packages and not the cause for these problems.
I tried other things like sudo pacman -Scc, sudo pacman -Syy, or sudo pacman -Sy archlinux-keyring. Every time something different might work, or the issue just goes away after some time. What is the cause, how can I fix it, and why is this happening so regularly? I’m talking multiple times a week on my end.
Well yes, the refresh keyrings errors obviously get solved by that. But as I said, they don’t fix the signature issue from the CachyOS repos, since that’s rather an issue stemming from these packages being installed from the AUR.
That’s weird, I just reinstalled proton-vpn-gtk-app from the AUR and the errors when running refresh keyrings are back. Did you also install those with paru, just in case the keyrings aren’t being handled correctly?
Sadly (or luckily I guess), the error is gone again, so I can’t really debug much any more. However, it is suspicious that I get this error for the core, extra, and multilib repo:
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for core repository
However, Pacman is running fine, so not sure if these are even issues.
Edit: Just so we’re on the same page. When you run the “Refresh keyrings” script in the CachyOS Hello application, you get no errors whatsoever, right?
I just confirmed on my other device and I see the same errors. So I think this is an issue with the AUR package.
I’m not a GUI type, 99% CLI, I can try though to check against what you see now.
Me neither, but this keyrings script is what the CachyOS staff recommended in other blog posts when having issues with the CachyOS certificate, which is why I tried it. Other than this script, the apparent lack of keyring files for the Proton VPN packages has caused me no issues so far.
==> ERROR: The keyring file /usr/share/pacman/keyrings/python-proton-linux.gpg does not exist.
==> ERROR: The keyring file /usr/share/pacman/keyrings/python-proton-linux-secretservice.gpg does not exist.
Press enter to exit
Well, since my original issue has been resolved (for now) all I can do is wait for it to happen again rather sooner than later probably. Thanks anyway for your help, and maybe someone else knows how to fix the CachyOS certificate issue reliably for the future.
Not sure whether this keyring problem should be reported to the AUR package, or if it’s rather a CachyOS issue. The package is quite popular on the AUR, so it would be weird that no one else has caught it yet. I didn’t see anyone reporting something that looks related.
I can confirm as a Regular Arch user, Ive not seen this on any other Install outside of CachyOS
sudo pacman-key --populate
[sudo] password for me:
==> Appending keys from archlinux.gpg...
==> Appending keys from cachyos.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2024-11-09
Same, since the original error with the CachyOS repos has once again resolved itself. I will try that the next time I run into this issue though
sudo pacman-key --refresh-keys did apparently change a bunch of keys, but the keyring issue with the proton-vpn packages are still unchanged.
Edit:
Yep, I m more used to Terminal commands, but Cachy OS Hello s pretty neat I must say, maybe @RayJW can alsotry to update Keys from the GUI.
The same goes for me, I only used the GUI because that’s what the CachyOS developers said to use when having issues with the repos and it didn’t help hence this post.
It definitely is for now, but as I stated in the original post the problem regularly returns and that’s why I wanted to see if anyone has the same problem or a reliable fix for the problem.
