package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255

Bug #795979 reported by WindTux
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

the error message appeared when starting session

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Jun 10 01:03:57 2011
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 255
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
WindTux (windtux) wrote :
affects: ubuntu → man-db (Ubuntu)
Revision history for this message
Robert Roth (evfool) wrote :

Can't exec "/var/lib/dpkg/info/man-db.config": Permission denied at /usr/share/perl/5.10/IPC/Open3.pm line 168.
open2: exec of /var/lib/dpkg/info/man-db.config configure /usr/share/man failed at /usr/share/perl5/Debconf/ConfModule.pm line 59
dpkg:error while processing man-db (--unpack):
  subprocess installed post-installation script returned error exit status 255

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.