On sunday, 15. Juli 2012, 11:26:11 Anne Wilson wrote:
>
> That's very interesting.
>
> I've known that happen in the past, but never seen any explanation for
> it. Please post the bug report number here so that others can follow it.
>
> Anne
I filed bug https://bugs.kde.org/show_bug.cgi?id=3035
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/07/12 11:17, Klaus Layer wrote:
> On sunday, 15. Juli 2012, 10:06:17 Anne Wilson wrote:
>> I'm not familiar with Kubuntu releases, so bear with me. If
>> Kubuntu supplies KGPG you can check there which keyserver it is
>> using and change it -
On sunday, 15. Juli 2012, 10:06:17 Anne Wilson wrote:
> I'm not familiar with Kubuntu releases, so bear with me. If Kubuntu
> supplies KGPG you can check there which keyserver it is using and
> change it - it may not be keys.gnupg.net. Kleopatra, on the other
> hand, appears to have a fixed setti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/07/12 09:38, Klaus Layer wrote:
> Hi,
>
> I am having trouble finding keys with kgpg 2.7.3 that is part of
> the Kubuntu 12.04 KDE packages. If I use the key server dialog and
> enter i.e. B973BA7B in the search field, it does not find the key
>
Hi,
I am having trouble finding keys with kgpg 2.7.3 that is part of the Kubuntu
12.04 KDE packages. If I use the key server dialog and enter i.e. B973BA7B in
the search field, it does not find the key on the key server keys.gnupg.net.
If I do the same directly with gpg it finds the key:
user@
