Upgrading gnupg yields kgpg during start to put our tons of lines like this : tfoerste@n22 ~ $ kgpg QDate::setYMD: Invalid date 1092-18-78 QDate::setYMD: Invalid date 9722-45-09 QDate::setYMD: Invalid date 9762-26-04 QDate::setYMD: Invalid date 1047-11-05 QDate::setYMD: Invalid date 9918-98-08 QDate::setYMD: Invalid date 1040-67-70 QDate::setYMD: Invalid date 8996-37-09 QDate::setYMD: Invalid date 1000-25-89 QDate::setYMD: Invalid date 1173-45-59 QDate::setYMD: Invalid date 1394-97-59 QDate::setYMD: Invalid date 7776-33-03 QDate::setYMD: Invalid date 9788-93-01 Furthermore kgpg column entries are missing (see screen shot) Reproducible: Always
Created attachment 185966 [details] screen shot
Confirmed, same here. (Mostly stable) amd64, problem occurs since gnupg update. app-crypt/gnupg-2.0.10 kde-base/kgpg-3.5.9
Ah yes, stable Gentoo x86, 2.6.27-gentoo-r10, KDE 3.5.10
Here too, amd64: sys-kernel/gentoo-sources-2.6.27-r8 app-crypt/gnupg-2.0.10 kde-base/kdeutils-3.5.9-r1
And I thought I did something wrong with my GPG keys... # qlist -CIve kgpg gnupg app-crypt/gnupg-2.0.11 kde-base/kgpg-3.5.10
I think it would make sense to change the bug summary to >=app-crypt/gnupg-2.0.10 : kgpg:3.5 fails to parse gpg keyring listing Cannot do it myself though... Toralf, what do you think?
(In reply to comment #6) > I think it would make sense to change the bug summary to .... > Toralf, what do you think? Feel free to do that :-)
I tried to recompile kgpg but I had no luck. The problem persisted.
I'm also not able to select GPG-Keys in Kopetes Cryptography-Plugin, could this have the same reason?
(In reply to comment #8) > I tried to recompile kgpg but I had no luck. The problem persisted. > Downgrading to gnupg-2.0.9 seems to be a workaround: $ qlist -CIv kdeutils gnupg app-crypt/gnupg-2.0.9 kde-base/kdeutils-3.5.9-r1 $ kgpg --version Qt: 3.3.8b KDE: 3.5.9 KGpg: 1.2.2 $ uname -a Linux jlc64 2.6.25-gentoo-r7 #1 SMP Thu Mar 19 21:40:09 PDT 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
arch x86, kgpg 3.5.9, gnupg 2.0.10, same problem here. using right click in konqueror and choosing action -> encrypt file (of course, encrypt with kgpg), I've not available public keys! it seems that recompile kgpg and gnupg doesn't help, same as moving out .gnupg directory, starting kgpg and then import public/private keys. gnupg (or better, gpg executable) works fine.
Reported upstream (gnupg developer mailing list and kde bugzilla). See also http://bugs.kde.org/show_bug.cgi?id=188473
I've got the same problem on amd64; in addition all the keys are gone when I open kgpg. When I hit "restore" key keys appear but the names, emails beside the keys are gone. The only stable version are the bone the has bugs: kgpg-3.5.9 Anybody knows how restore it to previous working version.
Indeed as gnupg-2.0.10 is buggy it has nothing to do with kgpg. downgrading to gnupg-2.0.9 solves the problem. Is anybody testing these applications before making them stable?
kgpg is not parsing the fixed-list/colon mode of gnupg correctly. In >=app-crypt/gnupg-2.0.10, --fixed-list-mode became the default when --with-colons was used, as the output otherwise was not well defined. If you used --fixed-list-mode already, then the output did NOT change. If you didn't then the output DID change. I direct you to gnupg-2.0.9/doc/DETAILS for the output format of fixed-list-mode. gnupg is not broken. kgpg just fails at parsing because it never used fixed-list-mode, and now it needs to. It's not limited to kgpg:3.5 either, I see kgpg-4.2* is broken as well. Of specific note to whomever goes to fix kgpg: 1. Check the format of timestamps before you try to parse them. There are _3_ valid formats. Unix epoch seconds ("192388500"), ISO8601 full ("19760205T091500") ISO8601 short date ("1976-02-05"). 2. The name for the key is not available on the pub record, it must be obtained from the uid record. As for testing, we run the gnupg testsuite with each release. We don't go and test every app that simply uses gnupg.
Yes, I can as KGpg maintainer confirm that this is a problem that needs to be fixed in KGpg. Please track the KDE bugtracker for this problem, the commits with the fixes will be noted there.
Unfortunately it will only be fixed in KDE-4.x or ?
(In reply to comment #17) > Unfortunately it will only be fixed in KDE-4.x or ? Well, the current patch is for KDE 4, but in the KDE Bugzilla, the comment says "Please test if this gives the same results as before and report back so I can backport this". So if someone manages to test the patch, it should get backported to KDE-3.
There is no patch for kde3 version, since upstream didn't care, and we can't do anything, so closing
It should be fixed at least in kde-base/kgpg:4.
Fixed in kde-base/kgpg-4.2.3-r1.
I was also trying to upload the patch, got weird CVS errors until i got a mail that the bug is fixed :P Thanks for the commit and sorry for the closing, i thought that the upstream commit was included in 4.2.3
BTW what's about people running 3.5.10 and 4.2. in parallel. Those should have sth like this, or ? /etc/portage/package.mask/misc:>app-crypt/gnupg-2.0.9
*** Bug 274915 has been marked as a duplicate of this bug. ***
Reopening as per the duplicate bug 274915.
*** Bug 274249 has been marked as a duplicate of this bug. ***
Created attachment 197345 [details, diff] Fixes parsing of gnupg’s output. I have created a patch for kgpg-3.5.10 that at least shows name and email of a key in the main window. No further testing has been done, also I can’t get it integrated into an ebuild (because of all that eclass stuff).
(In reply to comment #27) Please attach this patch also in upstream bug at: https://bugs.kde.org/show_bug.cgi?id=188473
(In reply to comment #28) > (In reply to comment #27) > > Please attach this patch also in upstream bug at: > https://bugs.kde.org/show_bug.cgi?id=188473 Done.
BTW b/c 3.5.10 depends on <=gnupg-2.0.9 I'm wondering why that was removed from the portage tree ...
=kde-base/kgpg-3.5* has been masked for removal. This bug won't be fixed.
