system-config-printer.py crashed with GError in populateList()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
Release is Karmic. Crash before window opens.
ProblemType: Crash
Architecture: i386
CupsErrorLog:
Date: Wed Nov 4 18:52:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Lpstat:
device for c3535: socket:
device for MP7802: usb://Canon/MP780
device for MP780_FAX: usb://Canon/
device for PIXMA_MP780: smb://SALT/
MachineType: ASUSTeK Computer Inc. VX2S
NonfreeKernelMo
Package: system-
PackageArchitec
Papersize: a4
PpdFiles:
MP7802: Canon PIXMA MP780 - CUPS+Gutenprint v5.2.4
c3535: Tektronix Phaser 850 Foomatic/Postscript (recommended)
MP780_FAX: Canon PIXMA MP780 - CUPS+Gutenprint v5.2.4 Simplified
PIXMA_MP780: Canon PIXMA MP780 - CUPS+Gutenprint v5.2.4 Simplified
ProcCmdLine: root=UUID=
ProcCmdline: python /usr/share/
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
dmi.bios.date: 07/17/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.
dmi.board.name: VX2S
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: VX2S
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
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 #438793, 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.