package tzdata 2018g-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tzdata (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This error seems to occur at every login attempt since the last update cycle.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: tzdata 2018g-0ubuntu0.
ProcVersionSign
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Tue Nov 13 19:41:41 2018
DuplicateSignature:
package:
Setting up tzdata (2018g-
Use of uninitialized value $ret in string eq at /usr/share/
dpkg: error processing package tzdata (--configure):
installed tzdata package post-installation script subprocess returned error exit status 128
ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128
InstallationDate: Installed on 2018-11-14 (11 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitec
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.0.5ubuntu5
apt 1.7.0
SourcePackage: tzdata
Title: package tzdata 2018g-0ubuntu0.
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Relevant dpkg terminal log lines:
``` 0ubuntu0. 18.10) ... perl5/Debconf/ FrontEnd/ Passthrough. pm line 134.
Setting up tzdata (2018g-
Use of uninitialized value $ret in string eq at /usr/share/
dpkg: error processing package tzdata (--configure):
installed tzdata package post-installation script subprocess returned error exit status 128
```
This particular bug has already been reported and is a duplicate of bug #1800065, 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.