After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554345 - msg is signed but there is no corresponding public key
msg is signed but there is no corresponding public key
Status: RESOLVED DUPLICATE of bug 624604
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[gpg]
Depends on:
Blocks:
 
 
Reported: 2008-09-29 18:51 UTC by Duncan Lithgow
Modified: 2012-06-18 10:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Duncan Lithgow 2008-09-29 18:51:11 UTC
Please describe the problem:
Ubuntu 8.04
Evolution 2.22.3.1

Evolution and Seahorse fail to fetch a matching public key.

Steps to reproduce:
1. I get a gpg signed message from someone whose public key is not in my keyring.
2. Evolution says "Signature exists, but need public key". When I click on the wax seal icon I get more information as below:

Actual results:
gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/duncan/.gnupg/gpg.conf'
gpg: armor header: Version: GnuPG v1.4.6 (GNU/Linux)
gpg: Signature made 2007-10-31T23:19:27 CET using DSA key ID 8AB6137F
gpg: Can't check signature: public key not found

* This information is either wrong or something is broken. The public key is on at least one of the listed key servers in Seahorse and Seahorse is set to automatically retrieve remote keys.

Expected results:
What I expected
* I get a gpg signed message from someone whose public key is not in my keyring.
* Evolution either
   * Retrieves the public from a key server and announces that the mess* age is signed correctly
   or
   * Tries to retrieve the public key, but something goes wrong, it tells me what has gone wrong ('Seahorse is not configured to automatically retrieve remote public keys. Please adjust your settings' or 'Seahorse reports that the remote public key is not found on the listed key servers')

Does this happen every time?
Yes

Other information:
In either case the current wording of the message is not useful, 'public key not found' does not help me solve the cause of the problem. did evolution try to find it? did seahorse tyr and fail? why was it not found?
Comment 1 André Klapper 2008-09-29 19:54:41 UTC
So Evolution uses Seahorse in your distribution? Interesting...
Comment 2 Bruce Cowan 2009-02-08 10:48:58 UTC
This sounds similar to bug 205718.
Comment 3 Duncan Lithgow 2009-02-09 21:51:45 UTC
Yes, similar. But I think bug 205718 is more a feature request. This bug report is because Evolution appears to be claiming to try something it isn't capable of , or just giving an use-less message when it doesn't work.
Comment 4 Shahar Or 2009-03-11 19:53:35 UTC
This bug occurs to me in Ubuntu 8.10.
Comment 5 Omer Akram 2010-06-08 09:07:12 UTC
Confirming in evo230
Comment 6 Omer Akram 2010-06-08 09:09:18 UTC
my bad, I am facing a different bug
Comment 7 Tom 2010-11-14 21:47:12 UTC
(In reply to comment #2)
> This sounds similar to bug 205718.

This is definitely not similar to bug 205718. It may be related to bug 624604 though.
Comment 8 André Klapper 2012-06-18 10:37:28 UTC
As bug 624604 would also fix this I will mark it as a dup.

*** This bug has been marked as a duplicate of bug 624604 ***