hpfax crashed with TypeError in __main__: not all arguments converted during string formatting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hplip
Unknown problem for me. The problem arose after I started the system.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: hplip 3.11.1-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CupsErrorLog:
W [11/Apr/
E [11/Apr/
E [11/Apr/
E [11/Apr/
W [12/Apr/
Date: Mon Apr 11 18:11:19 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for hp-LaserJet-1010: hp:/usb/
device for hp-LaserJet-1010-2: hp:/usb/
MachineType: ASUSTeK Computer Inc. K50IJ
Papersize: letter
PpdFiles:
hp-LaserJet-
hp-LaserJet-1010: HP LaserJet 1010, hpcups 3.11.1
ProcCmdline: python /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF8
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: hplip
Title: hpfax crashed with TypeError in __main__: not all arguments converted during string formatting
Traceback:
Traceback (most recent call last):
File "/usr/lib/
bug("Error importing HPLIP modules: %s\n" % (pid, e))
TypeError: not all arguments converted during string formatting
UpgradeStatus: Upgraded to natty on 2011-03-31 (11 days ago)
UserGroups:
dmi.bios.date: 08/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.
dmi.board.name: K50IJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K50IJ
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
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 #616450, 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.