apport package crashed on jaunty2karmic upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
I am new to this bug reporting thing and I only signed when I was prompted to do so after upgrading from Kubuntu 9.04 to Kubuntu 9.10. Immediately after rebooting the system I got a notification that apport-gtk crashed. I have no clue what was supposed to happen. I will reboot the system again to find out if I can reproduce the error. I will report it if it happens again.
Description: Ubuntu 9.10
Release: 9.10
apport:
Installed: 1.9.3-0ubuntu4
Candidate: 1.9.3-0ubuntu4
Version table:
*** 1.9.3-0ubuntu4 0
500 http://
100 /var/lib/
ProblemType: Crash
ApportLog:
apport (pid 31438) Fri Oct 30 02:31:55 2009: called for pid 31437, signal 6
apport (pid 31438) Fri Oct 30 02:31:55 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
apport (pid 31438) Fri Oct 30 02:31:55 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
600:1000:
600:1000:
Date: Fri Oct 30 03:39:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.9.3-0ubuntu4
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
LANGUAGE=
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-kde crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
XsessionErrors:
(polkit-
(nautilus:2200): Eel-CRITICAL **: eel_preferences
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 #471239, 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.