configure warnings and errors upon ./configure for Pinentry v0.9.7

Stephan Beck stebe at
Wed Nov 23 11:14:00 CET 2016


David Adamson:
> On Mon, Nov 21, 2016 at 8:15 PM, Stephan Beck <stebe at> wrote:
>> Ah, I forgot one thing: you have to add the following to your ~/.bashrc
>> file:
>> GPG_TTY=$(tty)
>> export GPG_TTY
>> Does it work now?
>> HTH
>> Stephan
> Stephan I updated the .bashrc file in my home directory, still got the
> same error, so I restarted the system but unfortunately the error
> remains.
> Thanks for the assistance.

You haven't answered the question if you only want to use text-mode.
If you only use text-mode, add those lines mentioned to ~/.bashrc (or
whatever may be your shell initialization file) and properly symlink
/usr/bin/pinentry to the pinentry-curses you actually would like to use
if you are using text-mode only, I don't know why it should not work.
I refer you to the info gnupg manual and its appropriate section
10.3 Commonly Seen Problems.
 * The Curses based Pinentry does not work

Maybe it's helpful for you and for all willing to help if you properly
document the output of gen-key with the debug flag set to expert or guru

gpg2 --gen-key --debug-level [expert|guru]

Just a suggestion.



P.S. I now see that you have installed gtk-pinentry, so maybe I was
wrong and you don't want to use text-mode.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x4218732B.asc
Type: application/pgp-keys
Size: 4089 bytes
Desc: not available
URL: </pipermail/attachments/20161123/29158e31/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20161123/29158e31/attachment.sig>

More information about the Gnupg-users mailing list