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
first boot after upgrade to 11.04
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: hplip 3.11.1-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CupsErrorLog: E [01/Apr/
Date: Fri Apr 1 12:00:09 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
Lsusb:
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: VMware, Inc. VMware Virtual Platform
Papersize: letter
PpdFiles:
HP_Deskjet_
VMware_
ProcCmdline: python /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=en.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-04-01 (0 days ago)
UserGroups:
dmi.bios.date: 12/31/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VMware Virtual Platform
dmi.product.
dmi.sys.vendor: VMware, 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.