Description of problem: The key set up to be used to sign the outgoing mail cannot be used as evolution never asks me for passphrase to unlock it and use it - instead upon pressing "Send" it stats that the key has been unsuccessfully unlocked 3 times and cannot be used and I should change my mail options. Version-Release number of selected component (if applicable): evolution-2.22.1-2.fc9.i386 How reproducible: Always Steps to Reproduce: 1. Use an account that has been already set up with PGP (in fedora 8 for example) 2. Create a new email and from the security select to sign with PGP 3. Press "send" Actual results: A new widows states that you have entered a wrong pass phrase for unlocking the key 3 times already and it cannot be used, and one should change the mail options Expected results: Evolution should as me for my pass phrase, unlock my key pair and sign my mail. It should also remember the pass phrase for the session if this option is selected. Additional info: might be in evolution data server but I am not sure how exactly all this works so I am submitting this as evolution bug
Was Evolution able to sign messages with the same key in Fedora 8? Could you try running Evolution from a terminal as follows, reproduce the problem you described, and post the output (after stripping any sensitive information): CAMEL_DEBUG="gpg:status" evolution You should see a bunch of messages that look like: status: [GNUPG:] ...
Yes, evolution was perfectly signing and encrypting mails in Fedora 8 with the same user account, I upgraded to F8 by installing on the root partition and keeping /home unchanged. Here is the output, I am not sure which of these is sensitive so.... The thing is it seems like evolution is trying some pass phrase but where does it get from? It never prompts me for such, and the error window is poped up immediately. status: [GNUPG:] USERID_HINT B80C147299C9CA42 P.J.Anakiev (Sysmaster) <pjanakiev> status: [GNUPG:] NEED_PASSPHRASE B80C147299C9CA42 B80C147299C9CA42 17 0 status: [GNUPG:] GET_HIDDEN passphrase.enter status: [GNUPG:] GOT_IT status: [GNUPG:] BAD_PASSPHRASE B80C147299C9CA42 status: [GNUPG:] USERID_HINT B80C147299C9CA42 P.J.Anakiev (Sysmaster) <pjanakiev> status: [GNUPG:] NEED_PASSPHRASE B80C147299C9CA42 B80C147299C9CA42 17 0 status: [GNUPG:] GET_HIDDEN passphrase.enter status: [GNUPG:] GOT_IT status: [GNUPG:] BAD_PASSPHRASE B80C147299C9CA42 status: [GNUPG:] USERID_HINT B80C147299C9CA42 P.J.Anakiev (Sysmaster) <pjanakiev> status: [GNUPG:] NEED_PASSPHRASE B80C147299C9CA42 B80C147299C9CA42 17 0 status: [GNUPG:] GET_HIDDEN passphrase.enter status: [GNUPG:] GOT_IT status: [GNUPG:] BAD_PASSPHRASE B80C147299C9CA42 Hope this helps
Evolution relies on an external GPG agent for passphrase storage. I believe Seahorse stores passphrases in the keyring. Other GPG agents just keep the passphrase in memory. From the output it looks like GnuPG no longer likes your passphrase for some reason. If you have Seahorse installed, see if you can find it in System -> Preferences -> System -> Keyring Manager.
RESOLVED: The thing is now that seahorse is integrated with the gnome desktop there are two sets for storing the passes - one called login which is automatically unlocked upon logging in and a second one called default (remaining from fedora 8) which actually keeps the info needed by evolution. This can be very frustrating - should be a special chapter in the user guide for this change!
Ah, thanks for the update. I've also been burned by the login/default keyring issue under different circumstances. Seems like something should have migrated the "default" keys to "login" after upgrading.