applet.py crashed with KeyError in get_notifications()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
This and other errors started popping up when I tried printing an email through evolution on a newly installed printer. Not sure what exactly caused it, but if I continue to get it I will send additional info.
This is on the development release of Ubuntu Destktop x86_64
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: system-
ProcVersionSign
Uname: Linux 2.6.35-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
CupsErrorLog:
Date: Sun Jul 11 22:50:02 2010
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Stylus-C88: usb://EPSON/
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitec
Papersize: letter
PpdFiles: Stylus-C88: Epson Stylus C88 - CUPS+Gutenprint v5.2.5 Simplified
ProcCmdLine: root=UUID=
ProcCmdline: python /usr/share/
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: system-
Title: applet.py crashed with KeyError in get_notifications()
Traceback:
Traceback (most recent call last):
File "/usr/share/
jobid = event['
KeyError: 'notify-job-id'
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 11/03/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: M3A770DE
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #602755, 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.