system-config-printer.py crashed with TypeError in getNetworkPrinterMakeModel(): cannot concatenate 'str' and 'list' objects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Druckerdialog --> Hinzufügen Netzwerkdrucker. Nach Eingabe der Mac-Adresse (Host) und Klick auf Vor erscheint Fehlermeldung.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: system-
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
CupsErrorLog: E [31/Jan/
CurrentDmesg:
[ 13.070875] NFSD: Using /var/lib/
[ 13.077765] NFSD: starting 90-second grace period
[ 15.621692] skge 0000:05:02.0: eth1: Link is up at 1000 Mbps, full duplex, flow control both
[ 23.624005] eth1: no IPv6 routers present
Date: Wed Feb 1 08:52:21 2012
DuplicateOf: https:/
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/python2.7
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: System manufacturer P5Q DELUXE
PackageArchitec
Papersize: a4
ProcCmdline: /usr/bin/python /usr/share/
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2201
dmi.board.
dmi.board.name: P5Q DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5Q DELUXE
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #924407, 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.