system-config-printer.py crashed with AttributeError in fillMakeList()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
The crash happened after I wanted to modify driver properties of the printer (Samsung CLX-2160N). Windows "Searching for drivers apperared for a short time" the the process crashed.
ProblemType: Crash
Architecture: i386
Date: Fri Sep 25 13:20:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Samsung: socket:
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc.
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Presario
Package: system-
PackageArchitec
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles: Samsung: Samsung CLX-216x Series (SPL-C)
ProcCmdLine: root=UUID=
ProcCmdline: python /usr/share/
ProcEnviron:
LANG=sl_SI.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape video www-data
dmi.bios.date: 11/25/2003
dmi.bios.vendor: Phoenix
dmi.bios.version: 0F0B
dmi.board.name: 07D4h
dmi.board.vendor: Compaq
dmi.board.version: KBC Revision: 1328
dmi.chassis.type: 10
dmi.chassis.vendor: Compaq
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.name: Presario
dmi.product.
dmi.sys.vendor: Compaq
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 #436218, 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.