Summary: | KMail2 4.14.3 cannot attach public keys when using GnuPG 2.1.0 | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Samir Nassar <samir> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | CC: | aheinecke, montel, samir |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 341501 | ||
Attachments: | Screenshot of error message |
Description
Samir Nassar
2014-12-02 14:34:19 UTC
Created attachment 89807 [details]
Screenshot of error message
I don't have gpg-2.1.0 on my computer but I will try to install it and look at it I can't reproduce this with current gnupg master. Maybe this is a manifestation of: https://bugs.gnupg.org/gnupg/issue1774 Do you have your public keyring in .kbx format? Do you have more then one key in your public keyring? (I'm Still using Kmail 4.13.3 but I doubt that the key access code has changed since then) I could try to reproduce this with gnupg 2.1.0 I do. On upgrading to GnuPG 2.1.0 I exported my public keys, private keys and trustdb, deleted .gnupg, and imported cleanly. $ pacman -Si gnupg Repository : core Name : gnupg Version : 2.1.0-6 Description : Complete and free implementation of the OpenPGP standard Architecture : x86_64 URL : http://www.gnupg.org/ Licenses : GPL Groups : None Provides : dirmngr gnupg2=2.1.0 Depends On : npth libgpg-error libgcrypt libksba libassuan pinentry bzip2 readline Optional Deps : libldap: gpg2keys_ldap libusb-compat: scdaemon Conflicts With : dirmngr gnupg2 Replaces : dirmngr gnupg2 Download Size : 1490.64 KiB Installed Size : 5916.00 KiB Packager : Gaetan Bisson <bisson@archlinux.org> Build Date : Fri 28 Nov 2014 08:46:53 PM CET Validated By : MD5 Sum SHA256 Sum Signature This bug is fixed with with GnuPG 2.1.1 and https://bugs.kde.org/show_bug.cgi?id=341501. |