package grub-pc 2.02~beta2-9ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #1451317 reported by Pankaj Kumar Dubey
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Invalid
High
Unassigned

Bug Description

Installation failed during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: grub-pc 2.02~beta2-9ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-52.85-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
Date: Mon May 4 09:04:21 2015
DuplicateSignature: package:grub-pc:2.02~beta2-9ubuntu1.1:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2014-06-05 (332 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=0af1702d-4309-4043-8ee2-887bc1b99d35 ro
SourcePackage: grub2
Title: package grub-pc 2.02~beta2-9ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Pankaj Kumar Dubey (dubepankaj1980) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

If you run update-manager again, does the package upgrade always crash the same way?

Aside from having -proposed packages enabled and this particular update failing, is your system fully up to date? Did this only just started happening, or is it likely it was happening before and you only just noticed?

This is a bug I've been tracking down for a little while, would you mind including the output of "dpkg -l" from your system so I can try to reproduce the same system state and further debug this?

Changed in grub2 (Ubuntu):
status: New → Incomplete
importance: Undecided → High
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
Yuriy Padlyak (gneeot)
Changed in grub2 (Ubuntu):
status: Expired → New
Revision history for this message
Phillip Susi (psusi) wrote :

Please don't reopen expired bugs without providing the requested information.

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