Ubuntu
xbmc package

package xbmc-live 2:11.0~git20120423.cd20772-1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 2

Bug #1016775 reported by Geoffrey Halfani Madsen on 2012-06-22

This bug report is a duplicate of: Bug #1071158: package xbmc-live 2:11.0~git20120423.cd20772-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2. Edit Remove

This bug affects 1 person

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

Bug Description

Dont know any more

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: xbmc-live 2:11.0~git20120423.cd20772-1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
Uname: Linux 3.2.0-25-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Sat Jun 23 00:38:10 2012
ErrorMessage: underproces installerede post-installation-script returnerede afslutningsstatus 2
InstallationMedia:

PackageArchitecture: all
SourcePackage: xbmc
Title: package xbmc-live 2:11.0~git20120423.cd20772-1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 2
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Geoffrey Halfani Madsen (geoffrey-halfani) wrote on 2012-06-22:

AptOrdering.txt Edit (614 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (343 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.8 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (83.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.2 KiB, text/plain; charset="utf-8")

Revision history for this message

papukaija (papukaija) wrote on 2013-05-06:

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 1071158, 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. Feel free to continue to report any other bugs you may find.