| Summary: | kmail keeps spawning "gpgsm --server" but never kills/reaps them | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Mike Frysinger <vapier> |
| Component: | crypto | Assignee: | David Faure <faure> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | brian.foster, direx, faure, jreznik, kde, kdenis, nsoranzo, rdieter |
| Priority: | NOR | ||
| Version: | 5.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/messagelib/14728b61a24f29afc2b3f8b86c26b410fdc27a0c | Version Fixed In: | 17.04 |
| Sentry Crash Report: | |||
|
Description
Mike Frysinger
2009-02-10 03:36:16 UTC
We've a user seeing this too: https://bugzilla.redhat.com/show_bug.cgi?id=495951 i just noticed that the issue seems to be better with kde-4.2.4 ... at least on my system, it seems to stabilize at a handful of gpgsm instances (like 6 of them), although it'd be nice if there werent any duplicate ones at all I'm so glad other people are seeing this, and it's not just me. I've been seeing this ever since I upgraded to KDE 4.1.1 from 3.5.10. Every signed message I view in KMail causes another gpgsm instance to be spawned. $ pgrep gpgsm | wc -l 203 There is apparently no practical limit on the number of these things that can be spawned. I almost never quit KMail, and I do see very few gpgsm instances running sometimes, so I have to guess that they do die off eventually. Nevertheless, KMail should be telling these things to terminate when it's finished with them, or else it should be reusing them rather than spawning new ones all the time. Perhaps it's trying to pool and reuse instances and just doing a lousy job? For what it's worth, they do terminate immediately if I quit KMail. I'm using KDE 4.3.1 (KMail 1.12.1) built from source by Gentoo's ebuilds. i dont have any gpgsm instances sticking around with kde-4.3.0, so perhaps there is interaction with something else non-obvious here ... I recently upgraded to Kubuntu 9.04 (yes, I'm a bit slow with the upgrades!), and am now also seeing this issue. $ kmail --version Qt: 4.5.0 KDE: 4.2.2 (KDE 4.2.2) KMail: 1.11.2 $ $ gpgsm --version gpgsm (GnuPG) 2.0.9 [ ... ] Home: ~/.gnupg Supported algorithms: Cipher: 3DES, AES, AES192, AES256, SERPENT128, SERPENT192, SERPENT256, SEED, CAMELLIA128, CAMELLIA192, CAMELLIA256 Pubkey: RSA, ECDSA Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, WHIRLPOOL Used libraries: gcrypt(1.4.1), ksba(1.0.3), assuan(1.0.5) $ I have a huge number of files of the general form (all of which date from after the upgrade to Kubuntu 9.04): ~/.gnupg/.#lk0x<HEX>.<NODE>.<NUM> I do not (knowingly) use gpg/gunpg/whatever-this-is, and have never (knowingly, or at least that I can recall ;-\ ) set it up. Hence, I presume, everything in ~/.gnupg/ is default? Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback. Still true under KMail 5 (here: 5.1.3). Confirmed by dfaure & me. Git commit 14728b61a24f29afc2b3f8b86c26b410fdc27a0c by David Faure. Committed on 03/04/2017 at 07:00. Pushed by dfaure into branch 'Applications/17.04'. Fix gpgsm processes being leaked due to QGpgME::KeyListJob not being deleted FIXED-IN: 17.04 M +2 -1 mimetreeparser/src/viewer/messagepart.cpp https://commits.kde.org/messagelib/14728b61a24f29afc2b3f8b86c26b410fdc27a0c |