Ubuntu
tzdata package

package tzdata 2010g-0ubuntu0.9.10 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 128

Bug #553781 reported by René Ramos on 2010-04-02

This bug report is a duplicate of: Bug #442941: debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tzdata (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: tzdata

Trying to install Vuze.

ProblemType: Package
Architecture: i386
Date: Thu Apr 1 22:41:46 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: el subproceso script post-installation instalado devolvió el código de salida de error 128
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: tzdata 2010g-0ubuntu0.9.10
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: tzdata
Title: package tzdata 2010g-0ubuntu0.9.10 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 128
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

René Ramos (notrum08) wrote on 2010-04-02:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (507 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (40.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-04-02:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 442941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.