Ubuntu
man-db package

package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el script post-installation se mató con la señal (Tubería rota)

Bug #798243 reported by Heimlich on 2011-06-16

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

I just can't install this software.

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 i686
AptOrdering:
menu: Install
startupmanager: Install
menu: Configure
startupmanager: Configure
Architecture: i386
Date: Thu Jun 16 09:07:14 2011
ErrorMessage: el subproceso instalado el script post-installation se mató con la señal (Tubería rota)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el script post-installation se mató con la señal (Tubería rota)
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Heimlich (jipr24) wrote on 2011-06-16:

Dependencies.txt Edit (780 bytes, text/plain; charset="utf-8")
Df.txt Edit (476 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (53.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (381 bytes, text/plain; charset="utf-8")

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.