Version: unspecified (using KDE 4.4.5) OS: Linux kgpg has problems to interpret the keyring properly. for the key that would be the last in my keyring if using the 'gpg -k' command kgpg shows me a key ID of '5889random usage'. Reproducible: Always Steps to Reproduce: open key list in kgpg / key properties dialog of last generated key. Actual Results: key ID of '5889random usage' additionally, in the key properties dialog, instead of a fingerprint for this key, kgpg shows me the letters "5889 rand om u sage". Expected Results: expected: the usual hex digits for the ID and the correct fingerprint the program versions: kgpg: 2.3.0 gnupg: 2.0.16-r1 note: the words "random usage" appear at the end of every gpg command, like this: gpg -k ... random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks the problematic key was the last one in the list gpg -k or gpg -K gives me, so it appears short before the line with "random".
Could you please attach the output of gpg -k --with-colons KEYID Where you replace KEYID with the correct fingerprint of the affected key.
thanks for your fast reply. here is the info you requested. sorry, but for privacy reasons I had to change some numbers in the fp and names, hope that doesnt affect the outcome. ~ $ gpg -k --with-colons 4205E835487E46C8 gpg: enabled debug flags: memstat trust extprog assuan tru::1:1282924547:1337428636:3:1:5 pub:u:3072:1:4205E835487E46C8:1281980131:::u:::scESC: uid:u::::1281980131::DA93A68C34E9A45358C2735012F4DD8B0FDBD85C::kristian (no.4) <kristian@xmail.li>: sub:u:3072:1:ED35E69BE4BCBD54:1281980131::::::e: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks what really confuses me now is that I generated another test key with the same parameters like the problematic one. now this testkey is the last in the list of keys and surprisingly kgpg has no problem to display this one correctly. BUT: the problematic one has still the malformed ID/FP. and I probably should also mention that I am unable to encrypt to the problematic key using kgpg (although cmdline-gpg does it flawless) and that kgpg can't display the subkey and (only sometimes) pops up an error message saying that it couldn't read pubkey when I close the properties dialog of that key.
I'm not sure where exactly the line breaks are. Can you please put the output in an attachment so I can feed it into my parser locally? Changing key ids or comments is no problem for the test.
Created attachment 51384 [details] output of gpg -k --with-colons note: if I pipe the output of the command to a file, it doesn't include the lines above and below the key information.
Created attachment 51385 [details] output of gpg -k --with-colons (2) that's why: this time I copied the output as it appears in the console into the txt-file manually.
So it's the debug flags that seem to confuse things. If you run it as "gpg --debug-level none -k --with-colons" it should not show any debug messages. I'll go and explicitely disable all debug messages when running gpg as a child of KGpg. If you would like to test: search for "--fixed-list-mode" in kgpginterface.cpp and append to both lines: << "--debug-level" << "none" before the semicolon.
SVN commit 1172517 by dakon: disable all debugging messages from GnuPG subprocesses They will be ignored in best case anyway and in worst case will confuse the parser. CCBUG:250348 M +1 -1 gpgproc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1172517
Thank you! I couldn't test it in the way you proposed since I am too familiar with tweaking packages before compiling (I have to let portage do the work). But I tested it via changing my ~/.gnupg/gpg.conf (setting debug level to none) and it worked - kgpg displays all keys correctly again. so this bug can be closed as resolved/fixed, right? never did that, but try...
Nope, I'll close the bug once that has been backported to the 4.5 (and maybe even 4.4) branch. But thanks for confirmation that this works now. I'll do some further testing and then backport the fix.
This completely breaks KGPG with gpg (GnuPG) 1.4.10, which has no --debug-level option. --debug is a valid option, though.
*** Bug 258252 has been marked as a duplicate of this bug. ***
*** Bug 258654 has been marked as a duplicate of this bug. ***
*** Bug 258872 has been marked as a duplicate of this bug. ***
SVN commit 1203734 by dakon: Check the GnuPG version first before setting the default arguments. GnuPG 1.x doesn't know about --debug-level which will cause it to fail. BUG:250348 M +26 -7 gpgproc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1203734
*** Bug 259310 has been marked as a duplicate of this bug. ***
*** Bug 259536 has been marked as a duplicate of this bug. ***
when will this be backported to the 4.5 series?
Next week.
*** Bug 259981 has been marked as a duplicate of this bug. ***
SVN commit 1206989 by dakon: bring the latest fixes and cleanups for gpgproc to 4.5 branch CCBUG:250348 M +30 -11 gpgproc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1206989