applet.py crashed with KeyError in _map_printer()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
I have a print job waiting with the printer name: "k'{iA..." (see attached screenshot)
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: system-
Uname: Linux 2.6.34-
Architecture: i386
Date: Wed Jun 23 11:14:08 2010
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
Lpstat:
device for HP-Color-
device for Officejet-
device for PDF: cups-pdf:/
Lsusb:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer, inc. TravelMate 4220
PackageArchitec
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles:
HP-Color-
PDF: Generic CUPS-PDF Printer
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: python /usr/share/
ProcEnviron:
PATH=(custom, user)
LANG=da_DK.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: system-
Title: applet.py crashed with KeyError in _map_printer()
UserGroups: adm admin cdrom dialout fuse lpadmin mythtv plugdev sambashare
dmi.bios.date: 06/23/06
dmi.bios.vendor: Acer
dmi.bios.version: v0.3122
dmi.board.name: Bodensee2
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: TravelMate 4220
dmi.product.
dmi.sys.vendor: Acer, inc.
tags: | removed: need-duplicate-check |
visibility: | private → public |
Changed in system-config-printer (Ubuntu): | |
status: | New → Incomplete |
Many thanks to have open this report to public visibility. My original bug report #602160 was automatically marked as duplicate of this present one.
I would like to help in finding the bug (my goal is to have the printer working again in the shortest time as possible). Please, tell me instructions: how could I help the debugging process?
Ciao.
CM