Summary: | Kleopatra crashes when trying to create New key pair | ||
---|---|---|---|
Product: | [Applications] kleopatra | Reporter: | stefanprobst |
Component: | general | Assignee: | Andre Heinecke <aheinecke> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kdepim-bugs, mutz, nasanone |
Priority: | NOR | ||
Version: | 3.0.1 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kleopatra/8e417cbfd52f88c4f114595b68e3f17a08c85d02 | Version Fixed In: | |
Sentry Crash Report: |
Description
stefanprobst
2018-01-21 18:55:50 UTC
Interestingly, generating a new key pair via kmail's "Add account" assistant *does* work - and then shows up in kleopatra. Hi, thanks for your report. Which Version in Neon is that exactly? Depending on the Neon flavor that can differ. (dpkg -s kleopatra) There was one crash that I know of that has been fixed with https://dev.gnupg.org/T3577 Kleopatra from KDE Applications 17.12.0 (There are Kleopatra 3.0.1 Versions both with and without this commit) If your Version is newer then from 17.12.0 please attach a backtrace. Thanks! This is with package version 4:17.12.1-0neon+16.04+xenial+build42. Backtrace: Thread 1 "kleopatra" received signal SIGSEGV, Segmentation fault. Kleo::gpgComplianceP (mode=mode@entry=0x672056 "de-vs") at /workspace/build/src/utils/gnupg-helper.cpp:284 284 /workspace/build/src/utils/gnupg-helper.cpp: No such file or directory. Oops. Looking at that code shows an obvious mistake that will lead to crashes against older GnuPG versions. (<2.1.16) I'll fix it. Git commit 8e417cbfd52f88c4f114595b68e3f17a08c85d02 by Andre Heinecke. Committed on 22/01/2018 at 14:24. Pushed by aheinecke into branch 'Applications/17.12'. Fix crash if compliance is not known to gnupg We need to check if entry is null because older gnupg versions might not have that config entry. M +6 -5 src/utils/gnupg-helper.cpp https://commits.kde.org/kleopatra/8e417cbfd52f88c4f114595b68e3f17a08c85d02 *** Bug 388047 has been marked as a duplicate of this bug. *** thanks guys the updated version works wonderfull - keep up the excellent work - hats off to you guys |