Ubuntu
grub2 package

package linux-image-2.6.32-23-generic 2.6.32-23.37 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2

Bug #639987 reported by Dart on 2010-09-15

This bug report is a duplicate of: Bug #537123: package linux-image-2.6.31-20-generic 2.6.31-20.57 failed to install/upgrade: /etc/grub.d/README executable bit set. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: grub2

ckage linux-image-2.6.32-23-generic 2.6.32-23.37 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-23-generic 2.6.32-23.37
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
Uname: Linux 2.6.31-21-generic i686
Architecture: i386
Date: Wed Sep 15 07:55:08 2010
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: grub2
Title: package linux-image-2.6.32-23-generic 2.6.32-23.37 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2

Tags:

Revision history for this message

Dart (dart-srk) wrote on 2010-09-15:

AptOrdering.txt Edit (649 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (46.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (150.6 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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 537123, 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.