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

Bug #1709723 reported by Conrad L Southworth
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
Undecided
Unassigned
plymouth (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

During a sudo apt autoremove apt would not progress. Got stuck at 44% then this bug appeared

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: grub-common 2.02~beta3-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Wed Aug 9 10:44:56 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-05-31 (70 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=dae22e96-ce5a-410c-95db-29bc246bcefe 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
Conrad L Southworth (contherad) 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 grub2 (Ubuntu) because there has been no activity for 60 days.]

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