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-
no further info available
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: system-
ProcVersionSign
Uname: Linux 2.6.35-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
CupsErrorLog:
E [09/Jul/
E [09/Jul/
Date: Fri Jul 9 13:13:45 2010
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Canon-iP3600-
Lsusb:
Bus 002 Device 004: ID 0573:4d20 Zoran Co. Personal Media Division (Nogatech) Hauppauge WinTV-USB II (PAL) with FM radio
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 04a9:10ca Canon, Inc.
Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP-Pavilion GL307AA-ABA a6123w
PackageArchitec
Papersize: letter
PpdFiles: Canon-iP3600-
ProcCmdLine: BOOT_IMAGE=
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 lpadmin plugdev sambashare
dmi.bios.date: 06/10/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.27
dmi.board.name: Nettle2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: GL307AA-ABA a6123w
dmi.sys.vendor: HP-Pavilion
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.