package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1846984 reported by Hasso
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tzdata (Ubuntu)
New
Undecided
Unassigned

Bug Description

got this bug by updating , I don't know any more than this

Relevant dpkg terminal log lines:

```
Current default time zone: 'Australia/Melbourne'
date: invalid date 'Sun Oct 6 02:23:37 UTC 2019'
dpkg: error processing package tzdata (--configure):
 subprocess installed post-installation script returned error exit status 1
```

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2019c-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189
Uname: Linux 4.4.0-165-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Sun Oct 6 13:23:37 2019
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-09-09 (392 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt 1.2.32
SourcePackage: tzdata
Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-09-09 (392 days ago)

Revision history for this message
Hasso (versand) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Benjamin Drung (bdrung) wrote :

Relevant dpkg terminal log lines:

```
Current default time zone: 'Australia/Melbourne'
date: invalid date 'Sun Oct 6 02:23:37 UTC 2019'
dpkg: error processing package tzdata (--configure):
 subprocess installed post-installation script returned error exit status 1
```

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 #1672111, 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.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.