package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[chris]

share/bleachbit/bleachbit/Command.py", line 131, in execute
    func_ret = self.func()
  File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
    raise RuntimeError(line)
RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", line 131, in execute
    func_ret = self.func()
  File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
    raise RuntimeError(line)
RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
Delete 1.1MB /var/cache/apt/archives

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libssl1.0.0: Install
 libssl1.0.0: Configure
 libssl1.0.0: Configure
 libssl-dev: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jun 8 12:29:11 2017
DuplicateSignature:
 package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8
 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ...
 dpkg: error processing package libssl1.0.0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2016-11-30 (190 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.