apport-gtk crashed with SIGABRT in raise()

[Eddie Kane]

another of multiple crashes, will fill out all bug reports then downgrade back to oneric

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CasperVersion: 1.304
CrashReports:
 640:0:0:7228096:2012-02-03 11:17:03.667556000 -0500:2012-02-03 11:17:04.667556000 -0500:/var/crash/_usr_share_apport_apport-gtk.0.crash
 640:0:0:133438:2012-02-03 11:16:38.299555033 -0500:2012-02-03 11:16:38.127555025 -0500:/var/crash/_usr_bin_lpstat.0.crash
 600:0:0:718195:2012-02-03 11:16:37.359555000 -0500:2012-02-03 11:16:38.359555000 -0500:/var/crash/cups.0.crash
 600:0:0:146620:2012-02-03 11:16:16.491554047 -0500:2012-02-03 11:16:16.483554046 -0500:/var/crash/resolvconf.0.crash
 600:0:0:150252:2012-02-03 11:06:57.571528000 -0500:2012-02-03 11:06:58.571528000 -0500:/var/crash/man-db.0.crash
Date: Fri Feb 3 11:16:59 2012
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: apport
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #901675, so 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.