Control: reassign 841909 842015 842334 pinentry-gnome3 0.9.7-6 Control: forcemerge 841909 842015 842334 Control: tag 841909 + patch pending
The three bugs above are all caused by a situation where the user wants
to use secret key material with gpg, while relying on pinentry-gnome3
with access to a d-bus session, but where that d-bus session has no
access to an expected GNOME session.
if pinentry-gnome3 knows that there is no d-bus session available, it
will fall back to curses.
But if it has access to a d-bus session where the Gcr prompter is
potentially active, it will try to use it, even if that Gcr prompter
cannot possibly display a prompt because no GNOME session is connected
to it. This is a bug in pinentry-gnome3, not a bug in gpg or gpg-agent.
I have a patch in the pipeline for pinentry-gnome3 that enables fallback
to curses in the situation where a d-bus session is available but Gcr
prompter is not.
--dkg
signature.asc
Description: PGP signature
