gpgme_op_keylist_start: error: Invalid crypto engine <GPGME>

[Hans-Christoph Steiner]

So the gpgme logging did give me some insight into what gpgme is doing,
from that I added 'g13' to the build, so now that's included.  But
unfortunately the log doesn't give any more detail about the "Invalid
crypto engine" error that is the show stopper.

I have the debug level set to 9, I think that's the highest level.  This
is what I get right before:

GPGME 2012-09-14 23:07:55 <0x0d6e>  gpgme_new: enter: r_ctx=0xbef116d4
GPGME 2012-09-14 23:07:55 <0x0d6e>  gpgme_new: leave: ctx=0x2a0d7f18
GPGME 2012-09-14 23:07:55 <0x0d6e>  gpgme_set_armor: call:
ctx=0x2a0d7f18, use_armor=1 (yes)
GPGME 2012-09-14 23:07:55 <0x0d6e>  gpgme_set_textmode: call:
ctx=0x2a0d7f18, use_textmode=1 (yes)
GPGME 2012-09-14 23:07:55 <0x0d6e>  gpgme_set_keylist_mode: call:
ctx=0x2a0d7f18, keylist_mode=0x5
GPGME 2012-09-14 23:08:11 <0x0d6e>  gpgme_op_keylist_start: enter:
ctx=0x2a0d7f18, pattern=search-tring, secret_only=0
GPGME 2012-09-14 23:08:11 <0x0d6e>  gpgme_op_keylist_start: error:
Invalid crypto engine <GPGME>

The whole log is attached.

.hc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpgme.log.bz2
Type: application/x-bzip
Size: 1069 bytes
Desc: not available
URL: </pipermail/attachments/20121016/28d444b4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 937 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20121016/28d444b4/attachment.pgp>