| Summary: | KGpg does not understand gpg's IMPORT_RES message | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | Tim Ruffing <public> |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | luke-jr+kdebugs |
| Priority: | NOR | ||
| Version: | 2.13.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kgpg/dfd166f04c2567133f06c1963f69dbdcb0a94030 | Version Fixed In: | 14.12.1 |
| Sentry Crash Report: | |||
| Bug Depends on: | |||
| Bug Blocks: | 340676 | ||
Git commit dfd166f04c2567133f06c1963f69dbdcb0a94030 by Rolf Eike Beer. Committed on 27/12/2014 at 18:36. Pushed by dakon into branch 'Applications/14.12'. fix importing keys using GnuPG 2.1 More fields at the end of GnuPG output may be introduced in new implementations and should just be ignored if they are not explicitely handled. FIXED-IN:14.12.1 M +1 -1 transactions/kgpgimport.cpp http://commits.kde.org/kgpg/dfd166f04c2567133f06c1963f69dbdcb0a94030 Thanks. :) *** Bug 352910 has been marked as a duplicate of this bug. *** |
When updating any key in KGpg, the operations succeeds, but I get the following message: The import result string has an unsupported format in line 2. Please see the detailed log for more information. Details: [GNUPG:] IMPORT_OK 0 53748A4029AE1B6A56BBB164A026540B4F26687B [GNUPG:] IMPORT_RES 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 This could be related to gpg 2.1: > gpg --version gpg (GnuPG) 2.1.1 libgcrypt 1.6.2