Ubuntu
grub2 package

debconf frontend lost X connection

Bug #668245 reported by Ewan Jeffrey on 2010-10-29

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

when updating to latest distribution

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: grub-pc 1.98+20100804-5ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Fri Oct 29 00:06:47 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
SourcePackage: grub2
Title: package grub-pc 1.98+20100804-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Ewan Jeffrey (ewan-navyblue) wrote on 2010-10-29:

AptOrdering.txt Edit (60.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (945 bytes, text/plain; charset="utf-8")
Df.txt Edit (512 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.4 MiB, text/plain; charset="utf-8")

Colin Watson (cjwatson) on 2010-11-25

summary:

- package grub-pc 1.98 20100804-5ubuntu3 failed to install/upgrade:
- subprocess installed post-installation script returned error exit status
- 1
+ debconf frontend lost X connection

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.