Ubuntu
tzdata package

package tzdata 2011g-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #816569 reported by ashwinjagadeesh on 2011-07-26

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

the bug basicaly is that i couldnt install any application fully and b4 it gets completed it exits with an error

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: tzdata 2011g-0ubuntu0.11.04
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AptOrdering:
tzdata: Configure
scite: Install
scite: Configure
Architecture: i386
Date: Tue Jul 26 23:38:54 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2011g-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

ashwinjagadeesh (ashwinjagadeesh) wrote on 2011-07-26:

Dependencies.txt Edit (561 bytes, text/plain; charset="utf-8")
Df.txt Edit (755 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (70.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Victor Vargas (kamus) wrote on 2011-07-26:

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 808164, 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.