This seems to be a race condition in debconf, not a bug in the postinst
script (which doesn't do anything very interesting).  I was able to
reproduce it only once.  The debconf frontend was blocked on read while
the postinst script had exited and was a zombie.

(I don't really understand this behaviour as read on a pipe should
return as soon as the process at the other end of the pipe exits.  So it
could even be a bug in the kernel, though that seems unlikely.)

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to