apport-gtk crashed with KeyError in __getitem__()

Bug #464127 reported by aggreyogoli
58
This bug affects 12 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

As soon as I had finished up-grading to Ubuntu 9.10 and rebooting I received this warning.

ProblemType: Crash
ApportLog:
 apport (pid 8327) Thu Oct 29 21:09:22 2009: called for pid 8325, signal 6
 apport (pid 8327) Thu Oct 29 21:09:22 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 8327) Thu Oct 29 21:09:22 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:29526:2009-10-29 22:36:29.000000000 -0500:2009-10-29 22:36:48.000000000 -0500:/var/crash/_usr_share_apport_apport-gtk.0.crash
 600:0:0:6893:2009-10-29 21:07:12.000000000 -0500:2009-10-29 22:35:37.000000000 -0500:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
Date: Thu Oct 29 22:36:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
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:

Revision history for this message
aggreyogoli (ojango) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
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.