[pkg-gnupg-maint] Bug#869416: Bug#869416: pinentry-gtk2: fails to request passphrase when importing OpenPGP secret key with Seahorse

NIIBE Yutaka gniibe at fsij.org
Tue Jul 25 02:39:24 UTC 2017


Hello,

intrigeri at debian.org writes:
>   gpg-agent[11835]: DBG: error calling pinentry: Inappropriate ioctl for device <Pinentry>

This error message is related to DISPLAY or GPG_TTY.

I guess that pinentry is invoked with no DISPLAY and no GPG_TTY.  It
failed to open window, and then, it failed at isatty (3), then return
ENOTTY (its error string: "Inappropriate ioctl for device").

>  * This problem doesn't happen when using pinentry-gnome3.
>    The difference I see in gpg-agent's debug log is that when using
>    pinentry-gnome3, I see a number of OPTION commands sent to
>    gpg-agent, e.g. OPTION display=:1, while I see no such thing when
>    using pinentry-gtk-2. I'm not sure who's responsible for sending
>    these options.

When DISPLAY is there for gpgme, gpgme sends "OPTION display=:1" to
gpg-agent.

Does Seahorse have DISPLAY env var?

>  * Importing the same key with gpg on the command line in GNOME
>    Terminal works just fine: the expected pinentry-gtk2 dialog is
>    displayed and the key is imported as a result.

I think that gpg has DISPLAY env var under GNOME Terminal.
-- 



More information about the pkg-gnupg-maint mailing list