gpa fails to deal with my key: Invalid crypto engine

[Jim Meyering]

Werner Koch wrote:
> On Sun,  4 Sep 2011 10:49, jim at meyering.net said:
>
>> Here's a reproducer that imports into an empty $HOME and .gnupg directory:
>>
>>     #!/bin/sh
>>     d=$(mktemp -d)
>>     echo $d
>>     mkdir -p $d/.gnupg
>>     export HOME=$d
>
> That makes X non working on my system.  Thus I used GNUPGHOME for a
> quick test. I found no problem with my current installation - however
> this is 2.1 and not 2.0.17.  I better test it on a plain amd64 box - but
> not today.
>
>> Here's the full log:
>
> I can't spot an obvious problem.  Debugging gpa might be easier for me.

Did you manage to reproduce the failure?

I've just built gnupg using the latest of all of these from git:

    gnupg
    libassuan
    libgpg-error
    libgcrypt
    libksba

(with the caveat that I had to work around a build failure due to
 libgcrypt's recent removal of gcry_md_start_debug, as I've just
 posted to gnupg-devel)

Even with that, I still end up with the pesky undismissable
"GPA error" dialog.

For the record, gpg2 now reports this:

    $ gpg2 --version
    gpg (GnuPG) 2.1.0-git0dcf517
    libgcrypt 1.6.0-gitba71277