I don't see any difference in behavior after updating to
libgpg-error-1.25 and `killall gpg-agent`. There are still at
least 10 seconds of this in watchgnupg:
4 - 13:09:53 gpg-agent[16749]: DBG: chan_9 -> S PROGRESS
need_entropy X 30 120
4 - 13:09:54 gpg-agent[16749]: DBG: chan_9 -> S PROGRE
Am 19.12.2016 um 02:20 schrieb Jan Kundrát:
> Hi,
> we're using gpgme's C++ bindings in Trojita [1], an IMAP e-mail client.
> After an update of gnupg from 2.1.15 to 2.1.16, gpg-agent appears to
> need more than 10s to initialize itself during startup -- or at least
> our very first decryptAndVer
On pondělí 19. prosince 2016 12:17:22 CET, Werner Koch wrote:
Plead use libgpg-error 1.25 and test again.
I don't see any difference in behavior after updating to libgpg-error-1.25
and `killall gpg-agent`. There are still at least 10 seconds of this in
watchgnupg:
4 - 13:09:53 gpg-agent[16
On Mon, 19 Dec 2016 02:20, j...@kde.org said:
> dev-libs/libgpg-error-1.24::gentoo USE="nls -common-lisp -static-libs"
Plead use libgpg-error 1.25 and test again.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpheYIxPnz1R.pgp
Description: PGP sign
Hi,
we're using gpgme's C++ bindings in Trojita [1], an IMAP e-mail client.
After an update of gnupg from 2.1.15 to 2.1.16, gpg-agent appears to need
more than 10s to initialize itself during startup -- or at least our very
first decryptAndVerify() operation takes more than 10s.
An initial re