package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1721925 reported by Atul Gupta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

upgrade stopped unexpectedly

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apache2 2.4.18-2ubuntu3.5
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
Apache2ConfdDirListing: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Oct 7 14:12:03 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-02-21 (228 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: apache2
Title: package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-03-02 (218 days ago)
modified.conffile..etc.apache2.apache2.conf: [modified]
mtime.conffile..etc.apache2.apache2.conf: 2017-07-22T18:51:06.896107

Revision history for this message
Atul Gupta (atulag) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Bryce Harrington (bryce) wrote :

It appears from the log that the error actually occurs prior to apache, due to some interdependency between plymouth and urandom. I think this is a dupe of plymouth bug 1646731

Setting up bluez (5.37-0ubuntu5.1) ...
insserv: warning: script 'S99runlcactivator' missing LSB tags and overrides
insserv: warning: script 'runlcactivator' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service plymouth and udev if started
insserv: loop involving service udev at depth 1
insserv: There is a loop at service runlcactivator if started
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!

affects: apache2 (Ubuntu) → plymouth (Ubuntu)
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.