Version: 1.13.5 (using KDE 4.4.5) OS: Linux When starting kwatchgnupg it adds a line log-file socket:///home/user/.gnupg/log-socket to ~/.gnupg/gpg.conf This makes gpg print the error message "cannot connect to home/user/.gnupg/log-socket" which in turn confuses kmail when parsing its output. From then on messages which are inline encrypted with gpg will not have a blue (nor green) frame around them nor any encrypted/signed icons in the message list. Reproducible: Always Steps to Reproduce: 1) Start kwatchgnupg 2) Look at message in kmail which is inline encrypted or signed inline.
The problem persists until I manually delete the log-file line from gpg.conf Thanks to Raimar Sandner for pointing me to the cause of the problem: http://homepage.uibk.ac.at/~c705283/archives/2009/05/24/kmail_inline_openpgp_silent_failure/index.html (am actually using KDE 4.5)
This still happens with KDE 4.8.0 ...
*** Bug 291890 has been marked as a duplicate of this bug. ***
I can confirm this bug (see bug 291890) and the described workaround.
still exists in kmail2 *** This bug has been marked as a duplicate of bug 291890 ***
Git commit 25f0b41941e093071cf9cee624b24f30a71047a1 by Sandro Knauß. Committed on 15/10/2013 at 16:44. Pushed by knauss into branch 'master'. use gpgme instead of kpgp for decrypting PGP Inline messages REVIEW: 113348 Related: bug 291890, bug 295217 FIXED-IN: 4.12 M +200 -149 messageviewer/viewer/objecttreeparser.cpp http://commits.kde.org/kdepim/25f0b41941e093071cf9cee624b24f30a71047a1