package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

[Damien Levac]

Was just trying to upgrade from 14.04 to 16.04 and the installer reported that issue and asked me to fill this...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
Date: Tue Jul 11 17:05:23 2017
DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess installed post-installation script returned error exit status 255
ErrorMessage: subprocess installed post-installation script returned error exit status 255
InstallationDate: Installed on 2013-09-06 (1404 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

[Damien Levac (proksima)]

I eventually succeeded to finish upgrading the system. The only thing I had to manually fix was to set TERM=xterm because the installer was not able to pop-up the purple selection screen with my self-compiled st terminal.

Do not know if this is related to this automatically generated bug report though...

[Seth Arnold (seth-arnold)]

Damien, interesting; did st provide terminfo pieces to install too?

Thanks

[Damien Levac (proksima)]

Of course and I've installed them on my main machine but that was an upgrade over SSH and the term info were not on that remote host. All in all, I think it was more my fault than anything else...

Maybe, to avoid this pitfall for other users, 'xterm' could be assumed if the TERM variable is not recognized? Otherwise I think this is a non-issue...

[Launchpad Janitor (janitor)]

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

[Adrien Nader (adrien)]

I'm marking this bug as Invalid for openssl due to the discussion above and the following line in DpkgTerminalLog.txt:

    Unknown terminal: st-256color

Debconf/whiptail failed and the issue seems to be in the machine configuration and/or whiptail/debconf rather than openssl. I'm not able to comment on the current status of these however.