Ubuntu
tzdata package

package tzdata 2011g-0ubuntu0.10.04 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 128 terug

Bug #787180 reported by Martin van den Brink on 2011-05-23

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

package crashes

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: tzdata 2011g-0ubuntu0.10.04
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
Date: Mon May 23 21:44:16 2011
ErrorMessage: subproces installed post-installation script gaf een foutwaarde 128 terug
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2011g-0ubuntu0.10.04 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 128 terug

Tags:

Revision history for this message

Martin van den Brink (mvdb63) wrote on 2011-05-23:

AptOrdering.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (495 bytes, text/plain; charset="utf-8")
Df.txt Edit (545 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (31.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (5.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-24:

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