package grub-common 2.02~beta3-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1707197 reported by Laurent Repond
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
Undecided
Unassigned
plymouth (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This occured when updating grub:

===========================================================================================

Setting up grub-common (2.02~beta3-4ubuntu2.2) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for grub-common.service failed because a timeout was exceeded.
See "systemctl status grub-common.service" and "journalctl -xe" for details.
invoke-rc.d: initscript grub-common, action "start" failed.
● grub-common.service - LSB: Record successful boot for GRUB
   Loaded: loaded (/etc/init.d/grub-common; generated; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2017-07-28 13:49:47 BST; 14ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 27354 ExecStart=/etc/init.d/grub-common start (code=killed, signal=TERM)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/grub-common.service
           └─27358 plymouth --ping

Jul 28 13:44:47 laurent-Inspiron-7559 systemd[1]: Starting LSB: Record successful boot for GRUB...
Jul 28 13:49:47 laurent-Inspiron-7559 systemd[1]: grub-common.service: Start operation timed out. Terminating.
Jul 28 13:49:47 laurent-Inspiron-7559 systemd[1]: Failed to start LSB: Record successful boot for GRUB.
Jul 28 13:49:47 laurent-Inspiron-7559 systemd[1]: grub-common.service: Unit entered failed state.
Jul 28 13:49:47 laurent-Inspiron-7559 systemd[1]: grub-common.service: Failed with result 'timeout'.
dpkg: error processing package grub-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-21ubuntu5) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up gdbserver (7.12.50.20170314-0ubuntu1.1) ...
Setting up syncthing-inotify (0.8.7) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Setting up google-chrome-stable (60.0.3112.78-1) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Setting up gdb (7.12.50.20170314-0ubuntu1.1) ...
Setting up libwhoopsie0:amd64 (0.2.55.1) ...
Setting up libxnvctrl0 (384.59-0ubuntu0~gpu17.04.1) ...
dpkg: dependency problems prevent configuration of grub-efi-amd64-bin:
 grub-efi-amd64-bin depends on grub-common (= 2.02~beta3-4ubuntu2.2); however:
  Package grub-common is not configured yet.

dpkg: error processing package grub-efi-amd64-bin (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub-efi-amd64:
 grub-efi-amd64 depends on grub-common (= 2.02~beta3-4ubuntu2.2); however:
  Package grub-common is not configured yet.
 grub-efi-amd64 depends on grub-efi-amd64-bin (= 2.02~beta3-4ubuntu2.2); however:
  Package grub-efi-amd64-bin is not configured yet.

No apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                                                            No apport report written because the error message indicates it's a follow-up error from a previous failure.
     dpkg: error processing package grub-efi-amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub2-common:
 grub2-common depends on grub-common (= 2.02~beta3-4ubuntu2.2); however:
  Package grub-common is not configured yet.

dpkg: error processing package grub2-common (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of shim-signed:
 shim-signed depends on grub-efi-amd64-bin; however:
  Package grub-efi-amd64-bin is not configured yet.
 shim-signed depends on grub2-common (>= 2.02~beta2-36ubuntu12); however:
  Package grub2-common is not configured yet.

dpkg: error processing package shim-signed (--configure):
 dependency problems - leaving unconfigured
Setting up whoopsie (0.2.55.1) ...
No apport report written because MaxReports has already been reached
                                                                    No apport report written because MaxReports has already been reached
                                                                                                                                        dpkg: dependency problems prevent configuration of grub-efi-amd64-signed:
 grub-efi-amd64-signed depends on grub-efi-amd64 (= 2.02~beta3-4ubuntu2.2); however:
  Package grub-efi-amd64 is not configured yet.

dpkg: error processing package grub-efi-amd64-signed (--configure):
 dependency problems - leaving unconfigured
Setting up nvidia-settings (384.59-0ubuntu0~gpu17.04.1) ...
No apport report written because MaxReports has already been reached
                                                                    Setting up python3-distupgrade (1:17.04.9) ...
Setting up python3-update-manager (1:17.04.4) ...
Setting up ubuntu-release-upgrader-core (1:17.04.9) ...
Setting up ubuntu-release-upgrader-gtk (1:17.04.9) ...
Setting up update-manager-core (1:17.04.4) ...
Setting up update-manager (1:17.04.4) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...
Errors were encountered while processing:
 grub-common
 grub-efi-amd64-bin
 grub-efi-amd64
 grub2-common
 shim-signed
 grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: grub-common 2.02~beta3-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Jul 28 13:49:47 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-04-14 (104 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=3de4752e-0b02-4888-9b03-5e489ab6e707 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: grub2
Title: package grub-common 2.02~beta3-4ubuntu2.2 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
Laurent Repond (laurentrepond) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in grub2 (Ubuntu):
status: New → Confirmed
tags: added: plymouth-ping
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please check to see if the command 'plymouth --ping' continues to hang in a terminal. In the event that it does it would help us out if you could run it under strace e.g. 'strace plymouth --ping' so that we can determine why the process is hanging. Thanks for your assistance!

Changed in grub2 (Ubuntu):
status: Confirmed → Incomplete
Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
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.