system-config-printer.py crashed with AttributeError in send_reply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
At login, apport prevent me about that error. I just had logged, opened firefox, and update-manager
ProblemType: Crash
Architecture: i386
Date: Fri Feb 26 22:36:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
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 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard Pavilion dv8000 (EK783EA#ABF)
Package: system-
PackageArchitec
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: python /usr/share/
ProcEnviron:
LANGUAGE=
LANG=fr_FR.utf8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: system-
Title: system-
Traceback:
Traceback (most recent call last):
File "/usr/share/
self.
AttributeError: '_IPPConnection
Uname: Linux 2.6.32-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/04/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.31
dmi.board.name: 309B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 49.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Pavilion dv8000 (EK783EA#ABF)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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 #520466, 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.