Ubuntu
grub2 package

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

Bug #595997 reported by James Greer on 2010-06-18

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

Grub update would not load via the updater. Sorry this is VERY new to me... I cannot give more info. First real try with Linux.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: grub-pc 1.98-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Jun 17 22:25:23 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-1ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

James Greer (xarak1) wrote on 2010-06-18:

AptOrdering.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (881 bytes, text/plain; charset="utf-8")
Df.txt Edit (596 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (48.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (40.2 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.