package man-db 2.5.9-4 failed to install/upgrade: subprocess script post-installation installé was killed by signal (Processus arrêté)

Bug #806315 reported by JPG
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

.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelModules: dm_raid45 xor btrfs zlib_deflate libcrc32c usbhid hid radeon ttm drm_kms_helper drm tg3 floppy i2c_algo_bit ramzswap xvmalloc
Architecture: i386
Date: Wed Jun 29 09:03:20 2011
ErrorMessage: subprocess script post-installation installé was killed by signal (Processus arrêté)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: subprocess script post-installation installé was killed by signal (Processus arrêté)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
JPG (jpg) 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.