| Summary: | Key signing does not work | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | Albert Astals Cid <aacid> |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 17.04 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kgpg/5d5b7c2a249094a4e284fad7dfc487dedc26c5ba | Version Fixed/Implemented In: | 17.08.0 |
| Sentry Crash Report: | |||
Git commit 5d5b7c2a249094a4e284fad7dfc487dedc26c5ba by Rolf Eike Beer. Committed on 29/07/2017 at 20:33. Pushed by dakon into branch 'Applications/17.08'. don't let signing be confused by KEY_CONSIDERED lines FIXED-IN:17.08.0 M +4 -0 transactions/kgpgsignkey.cpp https://commits.kde.org/kgpg/5d5b7c2a249094a4e284fad7dfc487dedc26c5ba |
Using gpg (GnuPG) 2.1.21 libgcrypt 1.7.8 I enabled some debug and get log_kgpg: KGpgSignKey(0x17c0abeb80) ("gpg", "-u", "3A6A4DB839EAA6D7", "--no-secmem-warning", "--no-tty", "--no-greeting", "--options", "/home/tsdgeos/.gnupg/gpg.conf", "--debug-level", "none", "--status-fd=1", "--command-fd=0", "--edit-key", "3588DA413C98979B", "sign", "save") gpg: enabled debug flags: memstat trust extprog log_kgpg: KGpgSignKey(0x17c0abeb80) "[GNUPG:] KEY_CONSIDERED 404138CB46E6B6362C9B356A3588DA413C98979B 0" log_kgpg: old 2 new 2 log_kgpg: KGpgSignKey(0x17c0abeb80) "quit\n" log_kgpg: sending quit log_kgpg: KGpgSignKey(0x17c0abeb80) "[GNUPG:] KEY_CONSIDERED CA262C6C83DE4D2FB28A332A3A6A4DB839EAA6D7 0" log_kgpg: old 2 new 2 log_kgpg: KGpgSignKey(0x17c0abeb80) "quit\n" log_kgpg: KGpgSignKey(0x17c0abeb80) "[GNUPG:] GET_BOOL sign_uid.okay" log_kgpg: KGpgSignKey(0x17c0abeb80) "YES\n" log_kgpg: KGpgSignKey(0x17c0abeb80) "[GNUPG:] GOT_IT" Should we get a keyedit.save.okay ?