package php7.2-common 7.2.5-0ubuntu0.18.04.1 failed to install/upgrade: installed php7.2-common package post-installation script subprocess returned error exit status 139
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
php7.2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Was attempting to install php with the command "apt-get install php".
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: php7.2-common 7.2.5-0ubuntu0.
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat May 19 16:00:43 2018
ErrorMessage: installed php7.2-common package post-installation script subprocess returned error exit status 139
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SourcePackage: php7.2
Title: package php7.2-common 7.2.5-0ubuntu0.
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Looks like something crashed in the middle of the installation:
Creating config file /etc/php/ 7.2/mods- available/ fileinfo. ini with new version
Segmentation fault (core dumped)
dpkg: error processing package php7.2-common (--configure):
installed php7.2-common package post-installation script subprocess returned error exit status 139
From the log it appears the crash occurred after the software was installed, either during or following configuration.
In dmesg it looks like perl crashed:
[ 7053.263108] frontend[5868]: segfault at 8000000000e ip 00005622558acfd5 sp 00007fff0a0df1a0 error 4 in perl[5622557cb0 00+1f8000]
perl is used in PHP's packaging scripts, so it makes sense that perl is the source of the crash, but unfortunately that doesn't help in pinpointing the reason for the crash.
Is there any chance you're able to reproduce this crash? I suspect this may either be infeasible to do, or the bug may be elusive, but if it can be reproduced it may be worth investigating. Otherwise, I don't think there is a good path to follow here.