Ubuntu
tzdata package

package tzdata 2010m-0ubuntu0.10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #661738 reported by Henrik Klausgaard on 2010-10-16

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

Binary package hint: tzdata

doing new installation into a ZOTAC MAG.
trying to install Ubuntu Restricted Extras failed.
will try again
Ubuntu 10.04.1 AMD64

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: tzdata 2010m-0ubuntu0.10.04
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Sat Oct 16 15:39:07 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2010m-0ubuntu0.10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Tags:

Revision history for this message

Henrik Klausgaard (henrikoffshore) wrote on 2010-10-16:

AptOrdering.txt Edit (3.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (495 bytes, text/plain; charset="utf-8")
Df.txt Edit (534 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (57.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (4.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Victor Vargas (kamus) wrote on 2010-12-30:

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