apport-gtk crashed with KeyError in __getitem__()

Bug #453593 reported by Vignesh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

Apport crashed while trying to report a problem about the hal crashing or something

My computer specs are:
Pentium 4 processor
Nvidia GeForce2 MX400 graphics card
Gigabyte GA-8IEXP motherboard
Netgear WG311v3 PCI wifi receiver (using ndiswrapper to get it working under Ubuntu 9.10)
1.5GB DDR RAM

ProblemType: Crash
ApportLog:
 apport (pid 14105) Sat Oct 17 09:27:52 2009: called for pid 14104, signal 6
 apport (pid 14105) Sat Oct 17 09:27:52 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 14105) Sat Oct 17 09:27:52 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:29512:2009-10-17 10:22:37.228131000 +1100:2009-10-17 10:25:03.404137083 +1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
 600:0:0:6892:2009-10-17 09:29:27.336204000 +1100:2009-10-17 10:22:07.752131244 +1100:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
Date: Sat Oct 17 10:22:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport-gtk 1.9.3-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Revision history for this message
Vignesh (vignesh-uses-ubuntu-deactivatedaccount) 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.