I've experienced KMail freezes multiple times which have been related to GnuPG not responding/waiting for a timeout etc. Such operations should be done in a separate thread or so, as it renders the whole KMail GUI unusable as nothing can be done at all until the timeout is reached, which might take up to 5 minutes in some cases (e.g. keyserver cannot be reached). Using KDE 4.8.0 an GnuPG 2.0.17.
""keyserver cannot be reached" how ? not network ?.
(In reply to comment #1) > ""keyserver cannot be reached" how ? not network ?. No local network issue - it seems the configured default keyserver was unreachable. Other servers were reachable and the issue could be solved temporarily by setting another default keyserver in kgpg, but this is no general solution to this issue.
I experienced the same problem. In my university network, the port for PGP keyserver search seems to be blocked. The result is a freezing kmail, which only gets usable again after a timeout (from kpgp?) has expired.
need to look at how to reproduce it
(In reply to comment #4) > need to look at how to reproduce it Simply use /sbin/iptables -A OUTPUT -p tcp --dport 11371 -j DROP to temporarily block all outgoing requests to PGP keyservers via hkp://.
Do you are talking about SMIME, PGP MIME or PGP Inline encrypted/signed messages?
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.