Hi Daniel,
I'm not sure if this helps, but using the connect manager gave an odd
result.
If I start connect manager, then gpg --send-key works immediately, it looks
just like your gpg-connect-agent output.
On another screen, I use gpg --send-key and that works. The key gets sent
and all is
Hi Dhole and Craig--
Thanks for your reports of dirmngr not responding. I've tried to
reproduce this bug, and actually found it easiest to reproduce with:
GNUPGHOME=$(mktemp -d) gpg-connect-agent --dirmngr
This should produce the following debugging info, followed by a "> "
prompt:
Hi,
I'm also experiencing this bug. I first noticed it while trying to
receive some keys with `gpg --recv-keys`. It just hangs. The same
happens with `caff`.
I managed to capture an strace with the following line:
`for i in `seq 0 1000`; do strace -o dirmngr.strace -f -tt -T -p $(pgrep
Package: dirmngr
Version: 2.1.15-4
Followup-For: Bug #840680
Possibly the same problem but --send-keys hangs most of the time and
never times out. At the same time dirmngr-client --ping also hangs.
I never seen so many ENOSYS before, this is stracing an existing
dirmngr so perhaps its the strace
On 2016-10-14 03:12:44 +0800, Shengjing Zhu wrote:
> After upgrade to 2.1.15-4, I find dirmngr is not always responding
> which makes command like `gpg --refresh-keys` stuck.
Same problem on a machine I upgraded a few days ago.
This does not occur on a machine which I have not upgraded yet
(I
Package: gnupg
Version: 2.1.15-4
Followup-For: Bug #840680
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm also affected. For the time being: `killall dirmngr' seems to help.
Unfortunately I didn't get any useful output setting the log level yet;
will try to provide some.
Regards,
Control: severity -1 grave
On Thu, 13 Oct 2016 19:16:56 -0400 Daniel Kahn Gillmor wrote:
> Control: tags 840680 + unreproducible moreinfo
> Control: severity 840680 important
Hello Daniel,
I am another user who's been bitten by this bug.
When the bug report severity was downgraded below the
> Thanks for this report. it sounds frustrating! I hope we can debug it:
>
> is this "always not responding" or "sometimes not responding"? I
> haven't observed the same behavior with dirmngr myself, so i'm not sure
> how to best proceed...
>
I find it is 'sometimes'. To describe it, I use
Control: tags 840680 + unreproducible moreinfo
Control: severity 840680 important
hi Shengjing--
Thanks for this report. it sounds frustrating! I hope we can debug it:
On Thu 2016-10-13 15:12:44 -0400, Shengjing Zhu wrote:
> After upgrade to 2.1.15-4, I find dirmngr is not always responding
>
Package: dirmngr
Version: 2.1.15-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrade to 2.1.15-4, I find dirmngr is not always responding
which makes command like `gpg --refresh-keys` stuck.
I test dirmngr with the following steps:
First run
10 matches
Mail list logo
