package libc-bin 2.23-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135

[Peter Cooper]

tried to update before installing o/s.I have had a long term problem with installing o.s and i thought maybe update before trying again.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libc-bin 2.23-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
Date: Sat Jan 13 10:45:09 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: subprocess installed post-installation script returned error exit status 135
JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code -7:
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: glibc
Title: package libc-bin 2.23-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135
UpgradeStatus: No upgrade log present (probably fresh install)

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1590744, so 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. Please continue to report any other bugs you may find.

[Peter Cooper (peter01510)]

Sorry Guys im not a computer wizard but i know my way around most of it.Im trying to load from a genuine usb stick to a brand new hard drive.

[Brian Murray (brian-murray)]

Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!