package man-db 2.6.0.2-2 failed to install/upgrade: subprocess script post-installation installé was killed by signal (Erreur de segmentation), informations de débogage écrites (« core dumped »)

Bug #860363 reported by Pierre
This bug report is a duplicate of:  Bug #1372673: excessive debconf use when triggered. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 11.10 is used as a VirtualBox guest

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: man-db 2.6.0.2-2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 27 10:27:15 2011
ErrorMessage: subprocess script post-installation installé was killed by signal (Erreur de segmentation), informations de débogage écrites (« core dumped »)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1)
SourcePackage: man-db
Title: package man-db 2.6.0.2-2 failed to install/upgrade: subprocess script post-installation installé was killed by signal (Erreur de segmentation), informations de débogage écrites (« core dumped »)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Pierre (pierred) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.