package grub-common 2.02~beta2-36ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1596133 reported by Lucas Braz Melo
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This bug appears in upgrade software.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-common 2.02~beta2-36ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Jun 25 00:17:24 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-07-06 (354 days ago)
InstallationMedia: It
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic root=/dev/mapper/it--vg-root ro drm.debug=0xe plymouth:debug
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: grub2
Title: package grub-common 2.02~beta2-36ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Lucas Braz Melo (lucasbrazmelo) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

The error in your log is:

Setting up grub-common (2.02~beta2-36ubuntu3.1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
insserv: warning: script 'K01.depend.stop' missing LSB tags and overrides
insserv: warning: script 'K01.depend.boot' missing LSB tags and overrides
insserv: warning: script 'K01.depend.start' missing LSB tags and overrides
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 .depend.boot and udev if started
insserv: loop involving service udev at depth 1
insserv: There is a loop at service plymouth if started
insserv: Starting .depend.boot depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Max recursions depth 99 reached
insserv: loop involving service thermald at depth 1
insserv: Starting .depend.boot depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: loop involving service mountkernfs at depth 1
insserv: There is a loop at service .depend.boot if started
insserv: Starting .depend.boot depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package grub-common (--configure):
 subprocess installed post-installation script returned error exit status 1

This shows that you have some sort of invalid local symlinks called 'K01.depend.stop', 'K01.depend.boot', and 'K01.depend.start' in one or more of the /etc/rc*.d/ directories on your system. These are invalid; the /etc/init.d/.depend.{boot,start,stop} files are configuration information for startpar, *not* init scripts, and creating init script symlinks to them is an error.

You will need to remove these invalid symlinks and re-attempt the upgrade.

This is not a bug in the grub package.

Changed in grub2 (Ubuntu):
status: New → Invalid
Revision history for this message
Alastair Carey (alastair-carey) wrote :

In my case, it was the init.d script for the Samsung Unified Print Driver that was causing the loop. Since the init.d script for that driver is only necessary when using an LPT port, I simply removed the script and the grub installation completed normally.

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.