Keyring gpg message spam

IslandC0der · 2021-08-19 01:43:09

Whenever I update my arch keyring, I get utterly flooded with:

gpg: checking the trustdb
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
(...)
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10

It still updates just fine, but I didn't use to have this issue, and it kinda bugs me
I've scoured the web looking for solutions, and it seems like a lot of people are having the same problem; but every time I see it, it's in some code output in a post for a completely different issue, where this just so happened to creep in, and it's never addressed.
I've reinstalled the keyring package, deleted the keyring and reinitialized and repopulated it... but alas, nothing works

Any ideas? Am I doomed to having to withstand this merciless flood every couple of months, watching powerlessly while my dear terminal drowns and succumbs to this tsunami of characters?

Last edited by IslandC0der (2021-09-14 00:03:31)

Lone_Wolf · 2021-08-21 12:26:01

Same here since june .

[2021-06-16T18:41:18+0200] [ALPM] upgraded archlinux-keyring (20210110-1 -> 20210616-1)
[2021-06-16T18:41:18+0200] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2021-06-16T18:41:20+0200] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2021-06-16T18:41:20+0200] [ALPM-SCRIPTLET] gpg: checking the trustdb
[2021-06-16T18:41:20+0200] [ALPM-SCRIPTLET] gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
[2021-06-16T18:41:20+0200] [ALPM-SCRIPTLET] gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
[2021-06-16T18:41:20+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10

It only happens with those 2 keys mentioned by OP .

Looking the keys up with pacman-key

# pacman-key --list-keys 1EB2638FF56C0C53 786C63F330D7CB92
pub   rsa2048 2011-06-25 [SC]
      487EACC08557AD082088DABA1EB2638FF56C0C53
uid           [ unknown] Dave Reisner <d@falconindy.com>
uid           [ unknown] Dave Reisner <dreisner@archlinux.org>
sub   rsa2048 2011-06-25 [E]

pub   rsa4096 2012-01-20 [SC]
      B5971F2C5C10A9A08C60030F786C63F330D7CB92
uid           [  full  ] Felix Yan <felixonmars@archlinux.org>
uid           [marginal] Felix Yan <i@felixc.at>
uid           [marginal] Felix Yan <yanran@deepin.com>
uid           [  undef ] Felix Yan <felixonmars@qq.com>
uid           [marginal] Felix Yan <felixonmars@163.com>
uid           [marginal] Felix Yan <felixonmars@nyaa.cat>
uid           [  full  ] Felix Yan <felixonmars@gmail.com>
uid           [marginal] Felix Yan <felixyan@bbtechgroup.com>
uid           [  undef ] Felix Yan <felixonmars@member.fsf.org>
uid           [marginal] Felix Yan <felixonmars@archlinuxcn.org>
uid           [  undef ] Felix Yan <felixonmars@fedoraproject.org>
uid           [marginal] keybase.io/felixonmars <felixonmars@keybase.io>
uid           [marginal] Yan, Ran (Name on Passport) <felixonmars@gmail.com>
uid           [ unknown] Felix Yan <yanran@uniontech.com>
uid           [ unknown] Felix Yan <felixonmars@189.cn>
uid           [ unknown] Felix Yan <felixonmars@ubuntukylin.com>
sub   rsa4096 2012-01-20 [E]

#

Both keys match with the ones shown on https://archlinux.org/master-keys/ .

Is this an issue in pacman / archlinux-keyring or user configuration error ?

Pryka · 2021-08-21 16:44:16

Same at least since june.

[2021-08-20T11:16:11+0200] [ALPM] upgraded archlinux-keyring (20210802-1 -> 20210818-1)
[2021-08-20T11:16:11+0200] [ALPM-SCRIPTLET] ==> Dodawanie kluczy z archlinux.gpg...
[2021-08-20T11:16:12+0200] [ALPM-SCRIPTLET] ==> Lokalne podpisywanie zaufanych kluczy w bazie...
[2021-08-20T11:16:12+0200] [ALPM-SCRIPTLET] ==> Importowanie zaufanych wartości właściciela...
[2021-08-20T11:16:12+0200] [ALPM-SCRIPTLET] ==> Wyłączanie unieważnionych kluczy w bazie...
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: sprawdzanie bazy zaufania
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
[2021-08-20T11:16:13+0200] [ALPM-SCRIPTLET] gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10

progandy · 2021-08-21 17:09:26

Maybe those two keys have an incomplete signature in the arch package. In a test keyring it looks like I can fix that by using --refresh-keys. My pacman keyring seems to be fine (maybe because I sometimes do that manually).

Last edited by progandy (2021-08-21 17:10:51)

IslandC0der · 2021-08-21 22:11:39

I've just ran pacman-key --refresh-keys, same output

Last edited by IslandC0der (2021-08-21 22:12:35)

GeorgeJP · 2021-08-22 13:24:06

Steps to resolve (all as root):

[1] Delete folder /etc/pacman.d/gnupg
[2] Initialize keyring

# pacman-key --init

[3] Populate keyring

# pacman-key --populate archlinux

[4] (optional) Reinstall archlinux-keyring

# pacman -S archlinux-keyring

Source: https://wiki.archlinux.org/title/Pacman/Package_signing

IslandC0der · 2021-08-22 16:58:07

Thank you, but like I said on #1: deleting, re-initializing and repopulating did not work, unfortunately

pptrx100 · 2021-08-30 15:43:51

I did what George JP said and it doesn't work but then ...
I don't know If I solved it but I've just installed gnupg [sudo pacman -S gnupg] and when I type [sudo pacman-key --list-keys] at the top the output [gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10] dissapeared
I had that trouble too [gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10] too

Last edited by pptrx100 (2021-08-30 15:44:13)

NiceGuy · 2021-09-13 19:07:24

This issue should be addressed by now. The pacman 6.0.1 release has fixes and should fix the spamming of trustdb checks.
Also upon reeading the corresponding commit messages, a performance benefit also got incorporated.

For those interested, here are the relevant commits:
https://gitlab.archlinux.org/pacman/pac … 114106a3a2 : pacman-key: Reduce gpg trustdb checks
https://gitlab.archlinux.org/pacman/pac … 7119185b67 : pacman-key: Add --quiet to a few more gpg invocations

IslandC0der · 2021-09-13 20:54:02

Sadly, nothing has changed
I tried what pptrx100 suggested, and I have pacman 6.0.1 installed.
If I downgrade archlinux-keyring and then update to the latest version, I'm still getting the same messages.
Alternatively, this also triggers it:

sudo gpg --homedir /etc/pacman.d/gnupg --check-trustdb --yes

IslandC0der · 2021-09-13 20:58:25

UPDATE: Nevermind! Nuking /etc/pacman.d/gnupg, and then recreating it with the latest version of pacman seems to have fixed it
Thanks everyone!

EDIT: Nope, not so fast: apparently I did initialize it, but forgot to repopulate it (facepalm)...
I got too excited, the issue still stands.

Last edited by IslandC0der (2021-09-14 00:03:09)

IslandC0der · 2021-09-14 00:11:30

Since this can be reproduced by running gpg directly, I'm pretty sure it's not a problem with pacman, but rather an issue with those keys in particular.

Allan · 2021-09-14 03:50:49

pacman-key quietens that output as it is unnecessary for the use pacman makes of the keyring.

Arch Linux

#1 2021-08-19 01:43:09

Keyring gpg message spam

#2 2021-08-21 12:26:01

Re: Keyring gpg message spam

#3 2021-08-21 16:44:16

Re: Keyring gpg message spam

#4 2021-08-21 17:09:26

Re: Keyring gpg message spam

#5 2021-08-21 22:11:39

Re: Keyring gpg message spam

#6 2021-08-22 13:24:06

Re: Keyring gpg message spam

#7 2021-08-22 16:58:07

Re: Keyring gpg message spam

#8 2021-08-30 15:43:51

Re: Keyring gpg message spam

#9 2021-09-13 19:07:24

Re: Keyring gpg message spam

#10 2021-09-13 20:54:02

Re: Keyring gpg message spam

#11 2021-09-13 20:58:25

Re: Keyring gpg message spam

#12 2021-09-14 00:11:30

Re: Keyring gpg message spam

#13 2021-09-14 03:50:49

Re: Keyring gpg message spam

Board footer