Bug 341501 - kmail2 4.14.3 fails to terminate gpg 2.1.0 instances on failed attempt to attach public keys
Summary: kmail2 4.14.3 fails to terminate gpg 2.1.0 instances on failed attempt to att...
Status: RESOLVED UPSTREAM
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on: 341490
Blocks:
  Show dependency tree / graph
 
Reported: 2014-12-02 20:01 UTC by Samir Nassar
Modified: 2014-12-15 20:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Samir Nassar 2014-12-02 20:01:44 UTC 
On attempting to attach public keys KMail2 issues what seems to be the following command: gpg2 --batch --no-sk-comment --status-fd 25 --no-tty --charset utf8 --enable-progress-filter --display :0 --export --armor -- EE76B39E07788F95F796B044FE679A908E997AB2

I issued 5 attempts to attach public keys to various emails and all give gpg2 commands are running and currently hidding my CPU hard.

Reproducible: Always

Steps to Reproduce:
1. Attach several public keys while GnuPG 2.1.0 is installed
2. All attempts fail
3. Listen for increased system activity

Actual Results:  
All called instances of gpg2 will be running in the background

Expected Results:  
KMail should have terminated the gpg2 instances.
Comment 1 Andre Heinecke 2014-12-03 10:28:47 UTC 
This also sounds to me like a manifestation of https://bugs.gnupg.org/gnupg/issue1774 exact pubkey search from Kmail triggering an endless loop in gnupg. I'll try to confirm this by going back to gnupg 2.1.0 if i find some time. With current master I can't reproduce this.
Comment 2 Andre Heinecke 2014-12-15 20:34:43 UTC 
Marking this as upstream as this will be fixed with the next gnupg release.

This also occurs when you are trying to export your key in kleopatra.