applet.py crashed with KeyError in refresh()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't know what happened except for the crash message. This happened a while after a resume from hibernate. The printer is on, but I'm not sure about he state of cups or the printer. There's a job stuck in the queue that I can see with the printer applet on the taskbar even after this crash.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: system-
ProcVersionSign
Uname: Linux 2.6.32-41-generic x86_64
Architecture: amd64
CupsErrorLog:
Date: Tue Jun 19 21:44:06 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Brother-MFC-7840W: lpd://BRN001BA9
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
PackageArchitec
Papersize: letter
PpdFiles: Brother-MFC-7840W: Brother MFC-7840W BR-Script3 , Postscript-Brother 20101122 (OpenPrinting LSB 3.2)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: python /usr/share/
ProcEnviron:
LANG=en_CA.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: system-
Title: applet.py crashed with KeyError in refresh()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 08/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.
dmi.board.name: 3627
dmi.board.vendor: Quanta
dmi.board.version: 18.42
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #768237, 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.