system-config-printer.py crashed with UnboundLocalError in on_tvNPDevices_cursor_changed()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
search printer
ProblemType: Crash
Architecture: i386
Date: Fri Sep 25 08:58:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
Lsusb:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
Package: system-
PackageArchitec
Papersize: a4
ProcCmdLine: root=UUID=
ProcCmdline: python /usr/share/
ProcEnviron:
LANGUAGE=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
Traceback:
Traceback (most recent call last):
File "/usr/share/
if host == None and device.type in ["socket", "lpd", "ipp"]:
UnboundLocalError: local variable 'host' referenced before assignment
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/24/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1104
dmi.board.name: P5VD2-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.sys.vendor: System manufacturer
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 #435740, 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.