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
This happened right after I booted Natty and logged into gnome.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: hplip 3.11.1-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CupsErrorLog:
CurrentDmesg:
[ 15.123968] EXT4-fs (sda8): re-mounted. Opts: commit=0
[ 22.050068] eth0: no IPv6 routers present
[ 22.404458] EXT4-fs (sda5): re-mounted. Opts: errors=
[ 22.407265] EXT4-fs (sda8): re-mounted. Opts: commit=0
Date: Sun Apr 17 16:17:25 2011
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-Color-
MachineType: OEM OEM
Papersize: letter
PpdFiles: HP-Color-
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: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: AB9 QuadGT (Intel965+ICH8R)
dmi.board.vendor: http://
dmi.board.version: 1.x
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: OEM
dmi.product.
dmi.sys.vendor: OEM
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.