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

Bug #1707809 reported by Alex Murray
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Invalid
Undecided
Unassigned
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Received error after installing latest updates.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-common 2.02~beta2-36ubuntu3.12
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-27-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug 1 09:57:09 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-02-07 (174 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-27-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: grub2
Title: package grub-common 2.02~beta2-36ubuntu3.12 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
Alex Murray (alexmurray) wrote :
tags: removed: need-duplicate-check
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: New → Incomplete
Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Alex Murray (alexmurray) wrote :

Hi Brian - I have since done a clean reinstall (due to this an other issues) and the issue is not present any more on the new installation (plymouth --ping is fine) - I wonder if something perhaps got corrupted in the old install?

Anyway, I appreciate you looking into it - will close as invalid.

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