[pkg-gnupg-maint] Bug#847552: Bug#847552: gnupg: decrypting after X pinentry is sometimes slow: around 10 seconds on a small file

[Werner Koch]

On Fri,  9 Dec 2016 13:04, vincent at vinc17.net said:

> $ gpg -d note.gpg
> gpg: AES encrypted data
> gpg: cancelled by user

"cancelled" was unfortunately a catch-all error of pinentries.  

> Note: I got this error immediately, and no windows are opened.
>
> A few minutes later, everything was OK.

That is strange.  It might be that the agent popped up a pinentry before
the one you used but for some reasons this did not show up on your
screen.  After a long timeout that invisible pinentry gets killed and
you get your pinentry.  Pinentry access is serialized.

Debug hint: Put

--8<---------------cut here---------------start------------->8---
log-file socket://
debug ipc
debug-pinentry
verbose
--8<---------------cut here---------------end--------------->8---

into gpg-agent.conf and restart the agent.  Then run in another xterm

  watchgnupg --force --time-only $(gpgconf --list-dirs socketdir)/S.log

to immediately see what the agent is doing.  it won't show confidential
stuff so you may even be able to post snippets from the output.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20161209/5e3e63d2/attachment.sig>