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

[keepitsimpleengr]

I was renaming a computer and the crash occurred.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: system-config-printer-gnome 1.2.3+20100723-0ubuntu8.2
ProcVersionSignature: Ubuntu 2.6.35-32.67-generic 2.6.35.14
Uname: Linux 2.6.35-32-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Apr 22 10:34:18 2012
ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for HPmg5320: cnijnet:/2C:9E:FC:0F:6E:F2
MachineType: EVGA 132-YW-E178-FTW
PackageArchitecture: all
Papersize: letter
PpdFiles: HPmg5320: Canon MG5300 series Ver.3.60
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic root=UUID=49494cf3-d878-4987-b93e-2e10ee46f1df ro delayacct
ProcCmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py']
SourcePackage: system-config-printer
Title: system-config-printer.py crashed with AttributeError in rename_printer()
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
dmi.bios.date: 01/23/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 132-YW-E178-FTW
dmi.board.vendor: EVGA
dmi.board.version: 1
dmi.chassis.type: 3
dmi.chassis.vendor: EVGA
dmi.chassis.version: 132-YW-E178-FTW
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/23/2009:svnEVGA:pn132-YW-E178-FTW:pvr1:rvnEVGA:rn132-YW-E178-FTW:rvr1:cvnEVGA:ct3:cvr132-YW-E178-FTW:
dmi.product.name: 132-YW-E178-FTW
dmi.product.version: 1
dmi.sys.vendor: EVGA

[Apport retracing service (apport)]

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 #726954, 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.