applet.py crashed with KeyError in refresh()

[c. mehlis]

Binary package hint: system-config-printer

clicked on the "show finished jobs" to make it active and hit the button again, then it crashes

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: system-config-printer-gnome 1.2.0+20100408-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
Architecture: amd64
Date: Tue Apr 13 19:22:13 2010
ExecutablePath: /usr/share/system-config-printer/applet.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for DESKJET-815C: hp:/usb/DeskJet_815C?serial=ES96B1C2P2IE
MachineType: Shuttle Inc SFM27
PackageArchitecture: all
Papersize: a4
PpdFiles: DESKJET-815C: HP Deskjet 815c hpijs, 3.10.2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=af651c9b-3ee8-4a80-bf7b-89a4bd6a3aa6 ro crashkernel=384M-2G:64M,2G-:128M quiet splash nmi_watchdog=1
ProcCmdline: python /usr/share/system-config-printer/applet.py
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/system-config-printer/applet.py']
SourcePackage: system-config-printer
Title: applet.py crashed with KeyError in refresh()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse pulse-access sambashare
dmi.bios.date: 10/03/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: SFM27
dmi.board.vendor: Shuttle Inc
dmi.board.version: V20
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: G5
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/03/2008:svnShuttleInc:pnSFM27:pvrV20:rvnShuttleInc:rnSFM27:rvrV20:cvnShuttleInc:ct3:cvrG5:
dmi.product.name: SFM27
dmi.product.version: V20
dmi.sys.vendor: Shuttle Inc

[Apport retracing service (apport)]

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 #561082, 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.