Version: 0.40 (KDE 3.x) (using KDE 4.7.1) OS: Linux starting watchgnupg out of kmail adds the following lines to gnupg.conf: debug-level basic log-file socket:///home/dust/.gnupg/log-socket whether on the commandline or in kgpg - the program doesn't start without outcommenting these lines again - kleopatra doesn't show the keys anymore but starts this is what kgpg or gpg on the commanline sais: gpg: /home/user/.gnupg/gpg.conf:248: argument not expected gpg: /home/user/.gnupg/gpg.conf:249: invalid option Reproducible: Always Steps to Reproduce: start watchgnupg out of kmail now following lines are added to your gnupg.conf: debug-level basic log-file socket:///home/dust/.gnupg/log-socket kleopatra starts but doesn't show the keys uncommenting the lines lets kleopatra start again showing the keys Actual Results: kleopatra starts but doesn't show the keys Expected Results: should start without any errors showing the keys OS: Linux (x86_64) release 3.0.0-12-generic Compiler: gcc
Confirmed this on the same system, which is Kubuntu Oneiric (11.10)
maybe the issue is affected by the gnupg package - kleopatra then should show an error like kgpg does.
Confirmed on FreeBSD 9-RC2
I had a look at this. It's actually not a kgpg problem specifically, it's Kgpg detecting a gpg error and bombing: When kgpg starts up, it does a 'gpg --version' and bombs out if it detects any errors since this change: commit db0b4afa84317182f48b6d8c3f603b0c96f5aff3 Author: Rolf Eike Beer <kde@opensource.sf-tec.de> Date: Sun Oct 23 21:14:02 2011 +0200 check for GnuPG errors on startup If GnuPG cannot run (e.g. because of configuration errors) everything bad can happen. Explicitely check for this on startup and tell the user to fix his GnuPG first. BUG:269459 FIXED-IN:4.7.3,4.8.0 CCMAIL:kde-i18n-doc@kde.org When I run that manually, I get: [mark@ ~/kgpg/kgpg]$ gpg --version gpg: /home/mark/.gnupg/gpg.conf:209: argument not expected gpg: /home/mark/.gnupg/gpg.conf:210: invalid option gpg (GnuPG) 1.4.11 I think it could be caused by having gpg and gpg2 installed and something getting confused. Either way, it doesn't look like a kgpg issue, more an issue with us creating gpg2 config items and them confusing gpg.
A workaround for KGpg is to configure it to use gpg2, which then will understand these options. But the problem indeed is that these lines should not be used in a configuration file used for gpg 1.x. Maybe watchgnupg should just do the same version check. And finally I know who broke all those GnuPG config files that lead to the KGpg bugs ;)
Looks like a dup of https://bugs.kde.org/show_bug.cgi?id=226630
*** This bug has been marked as a duplicate of bug 226630 ***