Ubuntu
man-db package

package man-db 2.5.7-2ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #863961 reported by Sarah Trichet-Allaire on 2011-10-01

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

maybe du to suppression of files in /var/cache

then, upgrade failed.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Tue Sep 27 08:31:24 2011
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
SourcePackage: man-db
Title: package man-db 2.5.7-2ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Tags:

Revision history for this message

Sarah Trichet-Allaire (sarah-trichet-allaire) wrote on 2011-10-01:

AptOrdering.txt Edit (218 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (811 bytes, text/plain; charset="utf-8")
Df.txt Edit (605 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (118.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (10.5 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.