gpgme-android dies when it needs pinentry

[Hans-Christoph Steiner]

On 06/19/2013 12:41 PM, Werner Koch wrote:
> On Wed, 19 Jun 2013 06:30, hans at guardianproject.info said:
> 
>> But for things like creating a new key, decrypting, signing, etc. gpgme always
>> crashes.  It does not seem to even try to launch pinentry, because we're not
>> seeing and logging from pinentry. Attached in the gpgme log for trying to
> 
> I can't see a gpgme crash for the log.  It might be a crash in gpg or
> gpg-agent.  Can you please check?  Having gpg-agent and gpg log files
> would also be useful.
> 
>> GPGME 2013-06-19 00:22:03 <0x4227>    _gpgme_io_read: enter: fd=0x2b, buffer=0x5c8339b0, count=1024
>> GPGME 2013-06-19 00:22:03 <0x4227>    _gpgme_io_read: leave: result=0
> 
> The first read of the status-fd returns 0, i.e. EOF.  That should not
> happen.
> 
> 
> Salam-Shalom,
> 
>    Werner


I just re-ran the gen-key procedure.  Looks like another Android doosie...
gpg2.log does not get created, gpg-agent.log is 0.  I included gpgme.log and
the Android logcat starting from when the app started till when it failed on
the key create.  Those are attached.

If you remember with other bits, we had to set LD_LIBRARY_PATH for things to
work, and we can't just set it on the app process because of Java
restrictions.  import, export, and gpgmeOpKeylist() all work, so I guess that
means LD_LIBRARY_PATH is correct.

I can't think of anything else.  But gpgme is consistently failing only on the
operations that require pinentry to get a passphrase.

.hc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gen-key-logs.tar.bz2
Type: application/x-bzip
Size: 9591 bytes
Desc: not available
URL: </pipermail/attachments/20130619/a4ae6655/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 939 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20130619/a4ae6655/attachment.sig>