Version: (using KDE KDE 3.4.92) Installed from: Gentoo Packages When I select a crypted or signed mail, kmail hangs and runs gpg --batch --decrypt and this process seems not to stop. The only way to stop it, is killing it via konsole. As I don't wanted to kill gpg every time I select a signed mail, I wanted to disable gpg completly for kmail. I opened configure dialog, deselected gpg, saved this setting and tried again to select a signed mail. No success. Kmail still starts gpg --batch --decrypt. Note that gpg is deselected! Is there any way to fix this problem? I'm running gpg 1.4.2-ecc0.1.6 from gentoo, but I don't think that it's gpgs fault that it is started even if it is deselected in kmail.
No, but gpg should be fixed to eventually finish running. If you wait for a few seconds, does the email show?
No, I waited about 1 minute, but no progress. KMail blocks as it is waiting for gpg to finish, the only way is to kill the gpg process. But I don't understand why kmail starts gpg even when I haven't checked it in the configure dialog. Btw, gpg-agent is running, could it be that kmail checks for a running gpg-agent and uses this one without checking the option in the configure dialog?
I don't know what's causing this. The Linux kernel version 2.6 has a problem with KMail + gpg in that the two processes fight for CPU usage for a few seconds. But your report seems to indicate that gpg simply sits there, doing nothing. In any event, KMail always decrypts and verifies signatures in every message, if it can. You can disable encryption/signing only.
Ah, ok. Hm...couldn't it be done, that kmail even doesn't try to verify signatures when gpg is disabled? I think it could be disabled by a use flag in gentoo at compile time, but it would be fine too, to disable it in running mode. I will try to boot another kernel, maybe the problem is really related to the kernel, cause I'm using 2.6.14-rc4-mm1 now. I will do a test with 2.6.14-rc5 and let you know if it works.
Same problem with 2.6.14-rc5. I don't know why, but it worked before! The first time I mentioned that it doesn't work any more, was after I wanted to check the gpg settings in the configure dialog. But I didn't changed anything and left all dialogs with abort. I installed gnupg-1.9.19 now for testing purpose, but it seems that kmail doesn't support this version yet. Is there any way how I can help to analyse the problem more detailed and provide more information?
current behaviour in kde 3.5.4: I disabled all crypto backends and have no gnupg package installed. kmail reports 6 times (i have 6 accounts) "GPGME: Ungültige Krypto-Engine" (translated: GPGME: invalid crypto-engine) in a popup message at startup.
Now in kde 4.1 it is possible to enable/disable every crypto engine used to encrypt/sign/verify the mails.
I'm using all aspects of gpg (signing, encrypting, decrypting) for a while now without a problem. Also disabling the gpg crypto backend in the settings didn't lead to problems. So I'm closing this.