[pkg-gnupg-maint] Bug#841143: race condition

[NIIBE Yutaka]

Hello,

I'm sorry I didn't put the context.  I am a developer of GnuPG and nPth.
I join the Debian GnuPG mailing list, so that development can go well.
Thus, I receive your bug report.  (I also maintain some packages in
Debian but most are not related to GnuPG.)

Since I felt that there is a kind of not-so-good communication in this
bug of #841143, I am trying to help.

Well, I would like to inform dkg that I review the Debian specific
patches, I mean, they are not ignored.

Ian Jackson <ijackson at chiark.greenend.org.uk> wrote:
> That's the symptoms I saw.  What version did you see this with ?

I'm testing with 2.1.7-2 in Stretch.  It is not reproducible (for me) by
upstream versions.

Today, I managed to have a concrete reproducible case.  Please find an
attached script (gpg-agent-locks-up.sh).

With GPGAGENT=/usr/local/bin/gpg-agent of upstream, the log is:
--------------------
2017-01-18 09:41:15 gpg-agent[4168] SIGTERM received - shutting down ...
2017-01-18 09:41:17 gpg-agent[4168] DBG: chan_9 <- [eof]
2017-01-18 09:41:18 gpg-agent[4168] gpg-agent (GnuPG) 2.1.18-beta70 stopped
--------------------

gpg-agent cleanly exits.

With the one in Stretch, the log is:
--------------------
2017-01-18 09:41:31 gpg-agent[4185] SIGTERM received - shutting down ...
2017-01-18 09:41:33 gpg-agent[4185] DBG: chan_9 <- [eof]
2017-01-18 09:41:36 gpg-agent[4185] SIGTERM received - still 0 open connections
2017-01-18 09:41:36 gpg-agent[4185] gpg-agent (GnuPG) 2.1.17 stopped
--------------------

It didn't exit even after "[eof]" and needed second SIGTERM.
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpg-agent-locks-up.sh
Type: text/x-sh
Size: 760 bytes
Desc: gpg-agent-locks-up.sh
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170118/53ea862f/attachment.sh>