apport-kde crashed with KeyError in __getitem__()

Bug #446915 reported by anurag@nehruplanetarium.org
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

This is my first time to use beta version of ubuntu. So, I am not pretty sure what happened exactly with this error. I just got a automatic reply about the apport stoped working.

and I am reporting the incidence in the hope this information may be of any use.

excuse me if its a repost.

ProblemType: Crash
Architecture: i386
CrashReports:
 600:1000:1000:1202438:2009-10-09 09:20:36.000000000 +0530:2009-10-09 09:20:37.000000000 +0530:/var/crash/_usr_bin_ksplashx.1000.crash
 600:0:0:1190579:2009-10-09 09:18:24.000000000 +0530:2009-10-09 09:19:32.000000000 +0530:/var/crash/_usr_bin_ksplashx.0.crash
 600:0:0:6853:2009-10-09 03:46:12.000000000 +0530:2009-10-09 09:20:07.000000000 +0530:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
 600:0:0:33938:2009-10-09 09:20:07.000000000 +0530:2009-10-09 09:20:24.000000000 +0530:/var/crash/_usr_share_apport_apport-kde.0.crash
Date: Fri Oct 9 09:20:07 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-kde
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.9.2-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_IN
 LANGUAGE=
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
PythonArgs: ['/usr/share/apport/apport-kde']
SourcePackage: apport
Title: apport-kde crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-12-generic i686
UserGroups:

Revision history for this message
anurag@nehruplanetarium.org (anurag) 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 #440373, 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.