system-config-printer.py crashed with AttributeError in on_printer_removed(): 'NoneType' object has no attribute 'name'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
printer not responding
tried to reinstall drivers for HP LaserJet P1005 and got this message
currently only from 'windoze' works...
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: system-
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Thu Mar 24 21:05:16 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP_LaserJet_P1005: hp:/usb/
MachineType: Acer TravelMate 2410
Papersize: letter
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles: HP_LaserJet_P1005: HP LaserJet p1005, hpcups 3.11.1, requires proprietary plugin
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
Traceback:
Traceback (most recent call last):
File "/usr/share/
if self.printer.name == printer:
AttributeError: 'NoneType' object has no attribute 'name'
UpgradeStatus: Upgraded to natty on 2011-01-03 (80 days ago)
UserGroups: adm admin audio cdrom dialout dip lpadmin netdev plugdev sambashare
dmi.bios.date: 02/07/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.09
dmi.board.name: Morar
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: TravelMate 2410
dmi.product.
dmi.sys.vendor: Acer
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 #741449, 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.