package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127

Bug #1872235 reported by BloodyIron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shared-mime-info (Ubuntu)
New
Undecided
Unassigned

Bug Description

When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-info broke the whole process throwing errors about libicu60, which was installed as new in the upgrade process. While the system was broken, I forced a reinstall of libicu60 (apt install --reinstall libicu60) which then allowed shared-mime-info to be installable.

As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here.

I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shared-mime-info 1.9-2
ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
Uname: Linux 4.4.0-177-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Sat Apr 11 13:33:07 2020
ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127
InstallationDate: Installed on 2016-03-14 (1489 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt 1.6.12
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127
UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago)

Revision history for this message
BloodyIron (bloodyiron) wrote :
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.