Ubuntu
console-setup package

package console-setup 1.25ubuntu4 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #334151 reported by Gavin Lynch on 2009-02-25

This bug report is a duplicate of: Bug #308466: package console-setup 1.25ubuntu4 failed to install/upgrade: subprocess post-installation script returned error exit status 1. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	console-setup (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: k9copy

as in summary

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: console-setup 1.25ubuntu4
PackageArchitecture: all
SourcePackage: console-setup
Title: package console-setup 1.25ubuntu4 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.27-11-generic i686

Tags:

Revision history for this message

Gavin Lynch (gavlynch) wrote on 2009-02-25:

Dependencies.txt Edit (1003 bytes, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (277.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-08-20:

The automated report seems to be a report about the console-setup package failing to upgrade.

summary:	- k9copy has a fatal error signal 11 (SIGSEGV) when creating an iso image - from a protected DVD + package console-setup 1.25ubuntu4 failed to install/upgrade: subprocess + post-installation script returned error exit status 1
affects:	k9copy (Ubuntu) → console-setup (Ubuntu)

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-08-11:

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