apport-gtk crashed with KeyError in __getitem__()

Bug #464077 reported by tyler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

It said something about nvidia i didn't really read it just submitted the bug... not really sure what I should put here. It happened upon the first boot of ubuntu 9.10.

ProblemType: Crash
ApportLog:
 apport (pid 23130) Thu Oct 29 19:04:57 2009: called for pid 23129, signal 6
 apport (pid 23130) Thu Oct 29 19:04:57 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 23130) Thu Oct 29 19:04:57 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:6857:2009-10-29 19:03:52.000000000 -0400:2009-10-29 22:58:13.000000000 -0400:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
 600:0:0:29930:2009-10-29 22:58:40.000000000 -0400:2009-10-29 22:58:49.000000000 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Thu Oct 29 22:58:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport-gtk 1.9.3-0ubuntu4
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.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: root

Revision history for this message
tyler (tjb2k3) 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.