Bug 190144 - KMail does not ask for GPG password without gpg-agent
Summary: KMail does not ask for GPG password without gpg-agent
Status: RESOLVED DUPLICATE of bug 167960
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: 1.11.2
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-20 10:55 UTC by Unknown
Modified: 2009-04-20 12:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2009-04-20 10:55:33 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

I can not use the decryption and signing functionality of kmail without having gpg-agent installed. The very first time after installing KDE4 that I touched an encrypted message (imported from an old installation), it asked me for a password (I don't know if it got correctly decrypted then as this "touching" was marking all messages of a folder as "Ham"). Since then, whenever I want to view an encrypted message or sign a message I send, it tells me the passphrase is wrong without even asking me. The configuration window of the OpenPGP crypto module is empty so I can't change anything there. KGpg can decrypt and sign messages without problems (it just asks me for the password each time, of course). After installing and setting up gpg-agent it now works in KMail, too, but I would really prefer to use it without having to manually set up anything, especially since that seems to be supported in theory.
Comment 1 Jaime Torres 2009-04-20 12:51:43 UTC
Thank you for taking the time to report this bug and helping to make KDE better. This particular bug has already been reported and is a duplicate of bug 167960, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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