apport-gtk crashed with KeyError in __getitem__()

Bug #451521 reported by Mike Murphy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

Crash report occurred upon startup. No visible errors on first triage, just sent this report.

ProblemType: Crash
ApportLog:
 apport (pid 23414) Wed Oct 14 13:45:05 2009: called for pid 23413, signal 6
 apport (pid 23414) Wed Oct 14 13:45:05 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 23414) Wed Oct 14 13:45:05 2009: Ignoring SIGABRT
Architecture: amd64
CrashReports:
 600:0:0:10529:2009-10-14 13:46:10.000000000 -0400:2009-10-14 14:23:54.000000000 -0400:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
 600:0:0:45539:2009-10-14 14:24:13.000000000 -0400:2009-10-14 14:24:38.000000000 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Wed Oct 14 14:24:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport-gtk 1.9.2-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

Revision history for this message
Mike Murphy (murph0613) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.