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

[Dan Drake]

Binary package hint: apport

During an upgrade of Natty beta I get:

Setting up apport (1.20.1-0ubuntu4) ...
Installing new version of config file /etc/default/apport ...
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
dpkg: dependency problems prevent configuration of apport-gtk:
 apport-gtk depends on apport (>= 0.41); however:
  Package apport is not configured yet.
dpkg: error processing apport-gtk (--configure):
 dependency problems - leaving unconfigured

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

Architecture: i386
CrashReports:
 600:1000:1000:21599197:2011-04-14 10:41:17.726547000 +0900:2011-04-14 10:41:22.954547522 +0900:/var/crash/_usr_lib_banshee_Banshee.exe.1000.crash
 600:0:0:454269:2011-04-21 09:18:28.309143000 +0900:2011-04-21 09:24:51.197142883 +0900:/var/crash/apport.0.crash
 600:1000:1000:10955558:2011-04-13 16:21:29.994437000 +0900:2011-04-13 16:21:34.130437447 +0900:/var/crash/_usr_bin_unity-2d-places.1000.crash
Date: Thu Apr 21 09:18:28 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
PackageArchitecture: all
SourcePackage: apport
Title: package apport 1.20.1-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Murray (brian-murray)]

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.