Ubuntu
man-db package

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

Bug #997824 reported by derrick b mach on 2012-05-10

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

it just popped up

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
Date: Wed May 9 09:59:44 2012
ErrorMessage: subprocess installed post-installation script killed by signal (Aborted)
InstallationMedia: Custom Live CD - Release i386
SourcePackage: man-db
Title: package man-db 2.5.7-2 failed to install/upgrade: subprocess installed post-installation script killed by signal (Aborted)

Tags:

Revision history for this message

derrick b mach (sinjnester) wrote on 2012-05-10:

AptOrdering.txt Edit (21.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (811 bytes, text/plain; charset="utf-8")
Df.txt Edit (612 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (36.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (27.9 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.