GNOME Bugzilla – Bug 545626
seahorse_keyset_pgp_signers_new returns 0 keys
Last modified: 2008-09-12 17:18:11 UTC
When attempting to sign a key the no keys usable for signing dialog is displayed. Signing files with seahorse-tool shows all uids for valid private gpg keys. Blocks work on bug #519825.
I'm not sure what's going on here. At first I thought maybe the usage was getting set wrong because I looked at a test key: gpg --edit-key 'fake 5' gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Secret key is available. pub 1024D/249F89F9 created: 2008-07-05 expires: never usage: SCA trust: ultimate validity: ultimate sub 2048g/4C058502 created: 2008-07-05 expires: never usage: E [ultimate] (1). fake 5 and thought maybe the key with usage: E was somehow overloading the one with SCA so I changed the flags in seahorse_keyset_pgp_signers_new to SKEY_FLAGS_CAN_ENCRYPT. No dice. I left it like that and used seahorse-preferences to set my default key to None. No dice. Changed the flags back and left my default unset. No dice. Stef, I think you need to take a look at this one.
Sorry missed this one. Looks like it was trying to match the key id instead of the 'tag' (ie: the type: PGP/SSH) 2008-09-12 Stef Walter <stef@memberwebs.com> * pgp/seahorse-pgp-keysets.c: Fix problem with 'no keys available' when trying to sign a PGP key. Fixes bug #545626