Ubuntu
tzdata package

package tzdata 2011j-0ubuntu0.11.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 128

Bug #864621 reported by Fernando on 2011-10-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)	New	Undecided	Unassigned

Bug Description

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: tzdata 2011j-0ubuntu0.11.04
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Wed Sep 28 01:00:50 2011
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2011j-0ubuntu0.11.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 128
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Fernando (fernando-lewandowski) wrote on 2011-10-02:

AptOrdering.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (565 bytes, text/plain; charset="utf-8")
Df.txt Edit (528 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (46.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-11-16:

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 #838956, 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. Feel free to continue to report any other bugs you may find.