Ubuntu
grub2 package

package grub-pc 1.98-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #621250 reported by knifeman1980@hotmail.com on 2010-08-20

This bug report is a duplicate of: Bug #511463: grub-pc failed to install/upgrade: exit status 1 - frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	grub2 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: grub2

Yesterday night (2010-08-20 00:30 AM)when I install the software I found the process was stood still 70% level for about 30 mins , so I turn off my PC.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: grub-pc 1.98-1ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Thu Aug 19 09:17:01 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: grub2
Title: package grub-pc 1.98-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

knifeman1980@hotmail.com (knifeman1980) wrote on 2010-08-20:

AptOrdering.txt Edit (12.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (893 bytes, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (86.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (48.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-06-21:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 511463, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.