Ubuntu
man-db package

package man-db 2.5.9-4 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Broken pipe)

Bug #774077 reported by Dan Porter on 2011-04-30

This bug report is a duplicate of: Bug #1372673: excessive debconf use when triggered. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	man-db (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: man-db

This bug occured when updating packages after a fresh 11.04 install on Thinkpad X61

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sat Apr 30 13:34:29 2011
ErrorMessage: subprocess installed post-installation script was killed by signal (Broken pipe)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Broken pipe)
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Dan Porter (stealthii) wrote on 2011-04-30:

AptOrdering.txt Edit (157 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (778 bytes, text/plain; charset="utf-8")
Df.txt Edit (453 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (62.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (713 bytes, text/plain; charset="utf-8")

Launchpad Janitor (janitor) on 2011-08-11

Changed in man-db (Ubuntu):
status:	New → Confirmed

Revision history for this message

Sérgio Faria (sergio91pt) wrote on 2011-09-16:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 617832, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Revision history for this message

Colin Watson (cjwatson) wrote on 2014-09-23:

Thanks for your report. The basic problem here is that man-db's trigger uses debconf to decide whether to update the manual page database, but debconf is not always reliably usable in triggers. I finally figured out a simple way to avoid this problem, which I'm tracking as bug 1372673. If you are still affected by this locally (which I realise is unlikely in the case of some of the older bugs of this type), then running "sudo dpkg --configure -a && sudo apt-get -f install" in a terminal should normally be enough to get the package management system back to a sensible state.