system-config-printer.py crashed with AttributeError in send_reply()

[ubername]

Binary package hint: system-config-printer

Trying to add printer attached to win7 box.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 9 19:24:18 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100228)
InterpreterPath: /usr/bin/python2.6
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Dell Inc. Dell DM061
Package: system-config-printer-gnome 1.1.17+20100217-0ubuntu2
PackageArchitecture: all
Papersize: a4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=e3aeb33f-1265-41b6-844e-317e5229aa20 ro splash
ProcCmdline: python /usr/share/system-config-printer/system-config-printer.py
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py']
SourcePackage: system-config-printer
Title: system-config-printer.py crashed with AttributeError in send_reply()
Traceback:
 Traceback (most recent call last):
   File "/usr/share/system-config-printer/asyncipp.py", line 192, in send_reply
     self._reply_handler (self._conn, result)
 AttributeError: '_IPPConnectionThread' object has no attribute '_reply_handler'
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/24/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0WG864
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd05/24/2007:svnDellInc.:pnDellDM061:pvr:rvnDellInc.:rn0WG864:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: Dell DM061
dmi.sys.vendor: Dell Inc.

[Apport retracing service (apport)]

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.