Ubuntu
man-db package

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

Bug #935235 reported by Jayant Sinha on 2012-02-18

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

This bug affects 2 people

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

Bug Description

Package failed to download

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Feb 18 19:26:49 2012
DpkgTerminalLog: Log started: 2012-02-18 19:26:40
ErrorMessage: subprocess installed post-installation script killed by signal (Broken pipe)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: man-db
Title: package man-db 2.5.7-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script killed by signal (Broken pipe)

Tags:

Revision history for this message

Jayant Sinha (jayant-sinha) wrote on 2012-02-18:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (809 bytes, text/plain; charset="utf-8")
Df.txt Edit (703 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (54.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-01-16:

Status changed to 'Confirmed' because the bug affects multiple users.

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

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.