hpfax crashed with NameError in bug()

[sasukeuni]

Binary package hint: hplip

help

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: hplip 3.10.6-1ubuntu10
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CupsErrorLog:
 E [28/Sep/2010:15:49:16 +0200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
 E [28/Sep/2010:15:53:53 +0200] [cups-deviced] PID 2324 (hpfax) stopped with status 1!
Date: Tue Sep 28 15:53:53 2010
ExecutablePath: /usr/lib/cups/backend/hpfax
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Deskjet-F300-series: hp:/usb/Deskjet_F300_series?serial=CN64AB629904KH
MachineType: HP Pavilion 061 ER038AA-ABE t3315.es
Papersize: a4
PpdFiles: Deskjet-F300-series: HP Deskjet f300 Series, hpcups 3.10.6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=97374863-e0fa-456b-88e6-eee02fe3a1ca ro quiet splash
ProcCmdline: python /usr/lib/cups/backend/hpfax
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF8
PythonArgs: ['/usr/lib/cups/backend/hpfax']
SourcePackage: hplip
Title: hpfax crashed with NameError in bug()
UserGroups:

dmi.bios.date: 03/24/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.48
dmi.board.name: AMETHYST-M
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.48:bd03/24/2006:svnHPPavilion061:pnER038AA-ABEt3315.es:pvr0ny0211RE101AMETM00:rvnMSI:rnAMETHYST-M:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: ER038AA-ABE t3315.es
dmi.product.version: 0ny0211RE101AMETM00
dmi.sys.vendor: HP Pavilion 061

[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 #646916, 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.