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 (Terminado (killed))

Bug #963889 reported by Ing. Pablo Fossati on 2012-03-24

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

mouse config

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-13.57-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
AptOrdering:
gcursor: Install
gcursor: Configure
Architecture: i386
Date: Sat Mar 24 10:07:19 2012
ErrorMessage: el subproceso instalado el script post-installation se mató con la señal (Terminado (killed))
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
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 (Terminado (killed))
UpgradeStatus: Upgraded to natty on 2012-03-23 (0 days ago)

Tags:

Revision history for this message

Ing. Pablo Fossati (ing-pablo-fossati) wrote on 2012-03-24:

Dependencies.txt Edit (796 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (68.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (549 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.