As example, after importing same keys from Bug 292405 - KGpg shows wrong key ID for certain keys (0x7282B245 and 0x7CD2EAED) and expanding the keys, the key signatures are display as they were generated by same key. gpg --list-sigs shows the right signatures. Reproducible: Always Steps to Reproduce: 1. Remove .gnupg folder 2. Create a new one executing gpg command 3. Start kgpg 4. Import keys 0x7282B245 and 0x7CD2EAED 5. On key manager, expand both keys in order to see key signatures and subkeys Actual Results: All key signatures as listed as if they were generated by same key (same Name, Email and ID). Expected Results: Right properties of each key used to signed the imported key should be shown. I will attach a screenshot from KGPG and the output from gpg --list-sigs.
Created attachment 71724 [details] gpg --lis-keys output
Created attachment 71725 [details] Kgpg window
Git commit 2d252cf08c51866a6acebe705db11b29941691bf by Rolf Eike Beer. Committed on 11/06/2012 at 19:29. Pushed by dakon into branch 'KDE/4.8'. fix key comparison returning wrong values This fixes a regression introduced in 4.8.2 with commit 2a100ae8d203107d17e438f67f65d26a4949cccc when trying to fix bug 292405. Related: bug 298465, bug 292405 M +7 -5 core/KGpgKeyNode.cpp http://commits.kde.org/kgpg/2d252cf08c51866a6acebe705db11b29941691bf
Wow, that was fast! Compiled, tested and running on my PC. Thank you!
*** Bug 302041 has been marked as a duplicate of this bug. ***
*** Bug 302782 has been marked as a duplicate of this bug. ***