Ubuntu
tzdata package

crash during update/package tzdata 2016c-0ubuntu0.15.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #1564114 reported by michele on 2016-03-30

This bug report is a duplicate of: Bug #1648556: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128. Edit Remove

This bug affects 1 person

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

Bug Description

cumputer ccrashed....(grey shadowed windos) and after long time of waiting...usually is just few seconds..it started going again..then update was request...but it couldt do it because keep crashing..

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: tzdata 2016c-0ubuntu0.15.10
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Mar 30 23:56:01 2016
DuplicateSignature: package:tzdata:2016c-0ubuntu0.15.10:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2016-02-01 (58 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.2ubuntu5.1
apt 1.0.10.2ubuntu1
SourcePackage: tzdata
Title: package tzdata 2016c-0ubuntu0.15.10 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

michele (italiaansedecoraties) wrote on 2016-03-30:

AptOrdering.txt Edit (1014 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (856 bytes, text/plain; charset="utf-8")
Df.txt Edit (599 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (97.4 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (15.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.9 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (32.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2016-03-30

tags:

removed: need-duplicate-check

Revision history for this message

Benjamin Drung (bdrung) wrote on 2023-01-10:

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Relevant log lines:

```
Setting up tzdata (2016c-0ubuntu0.15.10) ...
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 109.
dpkg: error processing package tzdata (--configure):
subprocess installed post-installation script returned error exit status 128
```

This particular bug has already been reported and is a duplicate of bug #1648556, 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.