I'm not sure. Earlier today the computer didn't waken up as usual, when I clicked the mouse, but revived when I pressed the ppwer button. It revived, but displayed a message saying that there was a system problem, and asked me if I wished to report it.

Bug #1795081 reported by Charles Ronald McMillan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tzdata (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm not sure. Earlier today the computer didn't waken up as usual, when I clicked the mouse, but revived when I pressed the ppwer button. It revived, but displayed a message saying that there was a system problem, and asked me if I wished to report it.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2018e-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 tzdata: Install
 tzdata: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Sep 28 23:29:35 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2018-07-29 (61 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.27
SourcePackage: tzdata
Title: package tzdata 2018e-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Charles Ronald McMillan (ronniemac) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Benjamin Drung (bdrung) wrote :

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

The relevant dpkg terminal log:

```
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.
```

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