Error message "buffer shorter than subpacket" when touching my keyring

Bug #52112 reported by Oliver Klee
2
Affects Status Importance Assigned to Milestone
gnupg (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gnupg

In my GPG keyring, I have 312 keys (including mine) and 71350 signatures. I regularly do a "--refresh-keys" to download new signatures.

For the last few days, I get the following error message (or warning) when doing anything with my keyring:

gpg: buffer shorter than subpacket
gpg: buffer shorter than subpacket
gpg: signature packet without keyid
gpg: buffer shorter than subpacket

(I refer to these four lines as "message block" further down.)

When doing gpg --rebuild-keydb-caches, I get this message block once.

When doing gpg --check-trustdb, I get this message block 6 times.

When doing gpg --refresh-keys, I get this message 10 times: Once at the beginning and 9 times at the end of the process.

I'm not really sure whether this really is a bug in gnupg or just a malformed key (and if so, how I can find out which key it is).

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

Oh, this is on Dapper i386 with current updates. I'm running kgpg in the background.

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

I've just purged my keyring of revoked/expired keys and of keys which I don't trust (yet). With these keys removed, the message disappears. I've backuped the old version of the keyring and of the trustdb so I'm able to reproduce the problem if needed.

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

This also causes bug 52113 (in PSI).

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Changed in gnupg:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

No, the problem seems to have disappeared with Feisty.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok, I'm marking this as fixed.

Changed in gnupg:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.