Ubuntu
man-db package

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

Bug #629413 reported by hallen on 2010-09-03

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)	New	Undecided	Unassigned

Bug Description

Binary package hint: man-db

An update failed to install.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: man-db 2.5.7-4
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
AptOrdering:
gwibber: Install
gwibber-service: Install
gwibber-service: Configure
gwibber: Configure
Architecture: amd64
Date: Thu Sep 2 22:39:47 2010
ErrorMessage: subprocess installed post-installation script killed by signal (Broken pipe)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
SourcePackage: man-db
Title: package man-db 2.5.7-4 failed to install/upgrade: subprocess installed post-installation script killed by signal (Broken pipe)

Tags:

Revision history for this message

hallen (hallen) wrote on 2010-09-03:

Dependencies.txt Edit (864 bytes, text/plain; charset="utf-8")
Df.txt Edit (625 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (87.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.5 KiB, text/plain; charset="utf-8")

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.