bug reporting applet crashed after upgrading to 9.10

Bug #467054 reported by Nikolai
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

I've just upgraded my home PC from 9.04 to 9.10, and after first boot got crash reporting applet active (displayed on top bar). Clicking on it resulted crash on some service, but report generation was aborted. After second click I've got to this point.
Sorry if this of no help for you.

ProblemType: Crash
ApportLog:
 apport (pid 26733) Sat Oct 31 18:10:10 2009: called for pid 26732, signal 6
 apport (pid 26733) Sat Oct 31 18:10:10 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 26733) Sat Oct 31 18:10:10 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:6853:2009-10-31 18:08:33.000000000 +0200:2009-10-31 19:05:32.000000000 +0200:/var/crash/_usr_lib_hal_scripts_hal_lpadmin.0.crash
 600:0:0:32626:2009-10-31 19:06:13.000000000 +0200:2009-10-31 19:06:23.000000000 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Sat Oct 31 19:06:14 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
Nikolai (nikolai-tkachenko) 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.