Arch Linux

v1s1n

Member

Registered: 2024-07-27

Posts: 3

[SOLVED] "Keyring is not writable"

Hey all!

Having a few issues with pacman today that I haven't seen before. pacman -Ss ethtool returns:

error: rumpowered: key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" is unknown
error: keyring is not writable
error: database 'rumpowered' is not valid (invalid or corrupted database (PGP signature))

Similarly,  pacman -Syu returns:

error: rumpowered: key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" is unknown
:: Import PGP key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx? [Y/n] y
error: key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" could not be imported
:: Synchronizing package databases...
core is up to date
 extra                              7.2 MiB   254 KiB/s 00:29 [#################################] 100%
 multilib                         138.0 KiB   325 KiB/s 00:00 [#################################] 100%
 rumpowered                         5.4 KiB  26.9 KiB/s 00:00 [#################################] 100%
error: rumpowered: key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" is unknown
:: Import PGP key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx? [Y/n] y
error: key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" could not be imported
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))

(removed keys, cuz i'm not sure what's private )
Tried to use pacman-key --list-keys to troubleshoot, but got:

gpg: Note: trustdb not writable
gpg: checking the trustdb
gpg: trustdb rec 30: write failed (n=-1): Bad file descriptor
gpg: trustdb: sync failed: Bad file descriptor
==> ERROR: A specified key could not be listed.

Any ideas? Not sure where to look. Thanks!

Last edited by v1s1n (2024-07-28 17:28:21)

v1s1n

Member

Registered: 2024-07-27

Posts: 3

Re: [SOLVED] "Keyring is not writable"

Extra info: pacman-key --init returns:

...
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keyring_get_keyblock failed: Invalid keyring
gpg: failed to rebuild keyring cache: Invalid keyring
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keydb_get_keyblock failed: Invalid keyring
gpg: validate_key_list failed
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keydb_get_keyblock failed: Invalid keyring

seems like a corrupted keyring, but i'm not sure how to fix it

Last edited by v1s1n (2024-07-27 20:50:53)

xerxes_

Member

Registered: 2018-04-29

Posts: 815

Re: [SOLVED] "Keyring is not writable"

Try this command, when you update:

sudo pacman -Sy archlinux-keyring && pacman -Syu

seth

Member

Registered: 2012-09-03

Posts: 59,882

Re: [SOLVED] "Keyring is not writable"

There's a good chance the keyring actually got corrupted.
https://bbs.archlinux.org/viewtopic.php … 6#p2082376

The currently problematic key is https://github.com/jc141x/rumpowered-pa … le#gpg-key (I guess) and I assume therefore https://keyserver.ubuntu.com/pks/lookup … 68b28a04b3 is the supersecret possibly private stuff you're hiding?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

v1s1n

Member

Registered: 2024-07-27

Posts: 3

Re: [SOLVED] "Keyring is not writable"

Try this command, when you update:

For future reference, this command can't pass because of said corrupted keyring. I ended up disabling rumpowered in pacman.conf and updating but it still doesn't go through. I had to remove /etc/pacman.d/gnupg and init/populate the keyring again. Probably a corrupted keyring, but it's all fixed now! Thanks y'all.

and I assume therefore https://keyserver.ubuntu.com/pks/lookup … 68b28a04b3 is the supersecret possibly private stuff you're hiding?

lol yup. i'm not a gpg person at all, can you tell?