[pkg-gnupg-maint] Bug#1079696: Bug#1079696: gpgconf: "gpgconf --kill all" infinite loop when /proc/fd is not available

Andreas Metzler ametzler at bebt.de
Tue Oct 7 18:04:33 BST 2025


On 2025-10-06 Steve McIntyre <steve at einval.com> wrote:
> Hey folks,

> I'm following up to the conversation here, as AFAICS the common factor
> in all the programs I list below is the use of libgpg-error...

...

> if we watch long enough, we can see that the loop here runs all the
> way up to 1073741816, which is the configured limit for open files on
> the system. This has changed from Bookworm to Trixie, I believe?

> Adding "ulimit -n 1024" to revert to Bookworm behaviour here makes
> things work in reasonable time.

> As far as we can tell, /proc is mounted just fine in the chroots when
> we're doing stuff here, so I'm not sure that the (non-)existence of
> /proc/self/fd is relevant to the behaviour we're seeing.

Today's 1.56 (not yet in Debian) has
 
 * Change the default method to get the number of fds to close.  This
   fixes a spawning problem on certain POSIX machine.  [T7696]

which might help.

cu Andreas



More information about the pkg-gnupg-maint mailing list