package apport 1.20.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
1) $ lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
2) $ apt-cache policy apport
apport:
Installed: 1.20.1-0ubuntu5
Candidate: 1.20.1-0ubuntu5
Version table:
*** 1.20.1-0ubuntu5 0
500 http://
100 /var/lib/
3) Expected the Update Manager to download and install latest development packages and install them.
4) Restarted system as requested by the Upgrade Manager, and got a dialog asking if I wanted to report the problem...
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: apport 1.20.1-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
ApportLog:
AptOrdering:
apport: Configure
apport-gtk: Configure
Architecture: i386
CrashReports:
600:1001:
600:1001:
600:1000:
600:0:
Date: Wed Apr 20 22:26:10 2011
DpkgTerminalLog:
Setting up apport (1.20.1-0ubuntu4) ...
start: Job failed to start
invoke-rc.d: initscript apport, action "start" failed.
dpkg: error processing apport (--configure):
subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110301.7)
PackageArchitec
SourcePackage: apport
Title: package apport 1.20.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2011-04-17 (4 days ago)
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.