Ubuntu
apport package

package apport 1.20.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #768669 reported by raydar on 2011-04-21

This bug report is a duplicate of: Bug #767829: package apport 1.20.1-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: apport

happens regularly on booting into Ubuntu 11.04

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: apport 1.20.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
ApportLog:

AptOrdering:
upstart: Install
upstart: Configure
apport: Configure
apport-gtk: Configure
Architecture: i386
Date: Wed Apr 20 19:12:03 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
PackageArchitecture: all
SourcePackage: apport
Title: package apport 1.20.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

raydar (raydar) wrote on 2011-04-21:

CrashReports.txt Edit (805 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.gz Edit (14.4 KiB, application/x-gzip)
DpkgTerminalLog.txt Edit (513 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-04-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 #767829, 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.