package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

Bug #1767453 reported by kevinred on 2018-04-27
112
This bug affects 23 people
Affects Status Importance Assigned to Milestone
ca-certificates (Ubuntu)
Undecided
Unassigned

Bug Description

Happened during upgrade to ubunut 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 17:51:26 2018
ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

kevinred (kevinred112) wrote :
tags: removed: need-duplicate-check
Brian Murray (brian-murray) wrote :

The fixed version of libssl is installed, and the error message is not about a duplicate certificate so this is not a duplicate of bug 1764848.

Updating certificates in /etc/ssl/certs...
rehash: skipping cacert.cer,it does not contain exactly one certificate or CRL
rehash: skipping req.pem,it does not contain exactly one certificate or CRL

Launchpad Janitor (janitor) wrote :

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

Changed in ca-certificates (Ubuntu):
status: New → Confirmed
miguelquiros (mquiros) wrote :

The bug appeared while upgrading from Ubuntu 16 to Ubuntu 18. It is a very serious bug, since many other packages depend on ca-certificates and were left unconfigured. Lots of error messages in the screen.
When the upgrade finished, the system was left in a very bad situation with so many non-configured packages. No workable reboot-shutdown button, not functioning menus ... If moving to a virtual terminal (Alt-F1) the virtual console did not work either, so the configuration error of ca-certificates is a really serious bug.
I did not dare to perform a hard poweroff and poweron because I was not confident that the system was going to be able to boot at all.
Fortunately enough, right clicking in the screen worked and I was able to open a terminal. From that terminal, I keyed firefox (not accesible through non-working menus) and downloaded from ubuntu archive the version 20170717 of ca-certificates and install it replacing the buggy 20180409 using dpkg -i.
After this, I performed
dpkg --configure -a
and all not-fully installed packages got correctly configured.
I had to poweroff via the button (no other choice) and when powering on again, Ubuntu 18 appeared with no other issue so far.

miguelquiros (mquiros) wrote :

I also tried to install version 20180409 after Ubuntu 18 was already working and the error is still there. It is not a problem of the upgrade procedure but a problem of the package itself.

Maurice (maurice-debijl) wrote :

Same here. I downloaded ca-certificates_20170717~16.04.1_all.deb from https://packages.ubuntu.com/xenial/all/ca-certificates/download

Then did a:
dpkg -i ca-certificates_20170717~16.04.1_all.deb
dpkg --configure -a

After that I did a:
sudo apt-get upgrade

Which upgraded to 20180409 without problems

miguelquiros (mquiros) wrote :

No success in my case (difference with Maurice report). Tried again today to upgrade (via dpkg -i) to 20180409 and got an error message saying that post-installation script produces an output status of "1" (this means error when executing the postinst script, doesn't it?). Package left unconfigured and 20170717~16.04.1 needs to be reinstalled to get a system without broken packages.
Is there some way to get more verbose information about what is going wrong with the post installation script?

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

Other bug subscribers