hpijs driver fails to work

Bug #212882 reported by Stefan Horning
2
Affects Status Importance Assigned to Milestone
HPLIP
Incomplete
Undecided
Unassigned

Bug Description

I have an HP-Deskjet 5550 Printer. In former times I always used the hpijs driver for it, like it was suggested by CUPS. It always worked just normally. But once the driver must have been broken. All the newer versions don't seem to work anymore. So I am always forced to use the Gutenprint driver. If I choose the suggested hpijs driver nowadays it never works. The job is never really sent to the printer and cups just deactivates the printer. It had been like this now, for at least a year and I didn't see any changes on this problem. It appeared on any distro and on different computers recently. I really wonder if I am the only one with this problem. It can't be any hardware or setup problem, because everything works fine as long I am not using hpijs. All the necessary packages are installed. I am running Ubuntu at the moment were everything is setup anyway. CUPS, Foomatic, hpilip, hpijs, everything is there. I would use the Gutenprint driver without mourning, but the results are pretty useless. Printing quality is too bad.
I am sorry I can't give any more debugging info except the printer Type and any recent Linux OS. But like I said the Problem appears anywere, so it's not a really specific bug.
Distros I have tried: Gentoo, Ubuntu, Arch-Linux

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

Please run hp-check -t and post the output.

Thanks!

Aaron

Changed in hplip:
status: New → Incomplete
Revision history for this message
Tla (innovatinggenius) wrote :

file "usr/bin/hp-check" line 161, in ?
core.init()

file "usr/hplip/installer/core_install.py", line 220 in init
self.version_description, self.version_public, self.version_internal= self.get_hplip()

file "usr/hplip/installer/core_install.py", line 220 in init
self.version_description, self.version_public, self.version_internal= self.get_hplip()
keyError: 'internal tag'

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.