gpg 1.2.2 update breaks kmail/cryptplugin?

[Ingo Klöcker]

--Boundary-02=_0SCI/xR3DHMq0yO
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 23 July 2003 09:49, Adrian 'Dagurashibanipal' von Bidder=20
wrote:
> After upgrading to gnupg-1.2.2-1 (Debian package), cryptplugin/kmail
> stopped working: gpg hangs with 100% CPU, and killing it produces the
> message 'the secret key belonging to the identity to be used to sign
> this message could not be found'. (Not exactly these words, sorry,
> this is from memory).
>
> Downgrading to 1.2.1-2 again helps. Anybody else had this? Do I need
> to recompile cryptplugin?

My guess is that you are being bitten by the following bug which has=20
been fixed in GnuPG 1.2.3 (which will hopefully be released very soon):
    * Listing keys is much faster again.

Simply compare the time that 'gpg --list-keys --with-colon' takes with=20
1.2.1 and with 1.2.2.

Since GnuPG 1.2.3rc1 has a bug which makes it impossible to fetch keys=20
from any keyserver (which has already been fixed in cvs) you should=20
continue to use GnuPG 1.2.1 until 1.2.3 is released.

Regards,
Ingo


--Boundary-02=_0SCI/xR3DHMq0yO
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)

iD8DBQA/ICS0GnR+RTDgudgRAvnmAJ4wlQyoxOCi6b5uGef5i7xbD2KPvgCg3FqU
4b4rKTKc8rFK/TmhYbsq3p8=
=mNYB
-----END PGP SIGNATURE-----

--Boundary-02=_0SCI/xR3DHMq0yO--