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

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

Bug Description

mistake installing jdownloader and in actualizations:

                              E: tzdata: el subproceso script post-installation instalado devolvió el código de salida de error 2
"compilation failed in require at usr/share/perl/5.10/POSIX.pm line 36

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Tue Dec 28 22:20:28 2010
ErrorMessage: el subproceso script post-installation instalado devolvió el código de salida de error 2
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: man-db
Title: package man-db 2.5.7-2 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 2

Revision history for this message
reciclaje (reciclaje3) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

affects: ubuntu → man-db (Ubuntu)
security vulnerability: yes → no
visibility: private → public
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.