Ubuntu
man-db package

package man-db 2.6.1-2 failed to install/upgrade: el subproceso instalado el script post-installation se mató con la señal (Terminado)

Bug #1040178 reported by Silvio Solano on 2012-08-22

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

I am new in linux, I really don't undestend too mucho, even I don't understaing the englis properly.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.1-2
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Mon Aug 20 10:59:39 2012
ErrorMessage: el subproceso instalado el script post-installation se mató con la señal (Terminado)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
SourcePackage: man-db
Title: package man-db 2.6.1-2 failed to install/upgrade: el subproceso instalado el script post-installation se mató con la señal (Terminado)
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Silvio Solano (ssgarciacu) wrote on 2012-08-22:

AptOrdering.txt Edit (3.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (668 bytes, text/plain; charset="utf-8")
Df.txt Edit (404 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (66.1 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (77.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (10.4 KiB, 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.