Ubuntu
man-db package

package man-db 2.5.7-2ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255

Bug #869654 reported by Thiago Cristoni on 2011-10-07

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

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

3) What you expected to happen
Don't know

4) What happened instead
This problem appear

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic i686
Architecture: i386
Date: Thu Oct 6 23:03:16 2011
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 255
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
SourcePackage: man-db
Title: package man-db 2.5.7-2ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255

Tags:

Revision history for this message

Thiago Cristoni (thihenrique) wrote on 2011-10-07:

AptOrdering.txt Edit (231 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (811 bytes, text/plain; charset="utf-8")
Df.txt Edit (512 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (37.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (3.7 KiB, application/x-gzip)

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.