[Bug 283343] keys aren't shown anymore after starting watchgnupg

[mnd999 at gmail.com]

https://bugs.kde.org/show_bug.cgi?id=283343


mnd999 at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kde at opensource.sf-tec.de




--- Comment #4 from  <mnd999 gmail com>  2011-11-22 19:53:07 ---
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 at 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 at 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.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.