HPLIP

Laserjet CP1025 fails printing

Asked by Ahronovitz

Hello,
I reported the bug #1907444 and got a reply by mail, pointing to similar bugs and suggesting a possible correction that is not satisfactory.
As suggested, I did the "correction" suggested hereafter, and there is some evolution, but it still remains buggy.

The "correction" suggested :

one possible fix is to edit /usr/share/hplip/data/models/models.dat and alter
[hp_laserjet_cp1025] to [hp_laserjet_cp_1025].

And the result is :
- the printer is recognized (wow, this is new) and prints a test page (ugly), also prints a requested page (ugly, especially for black printing),
- BUT if I switch the color selection from color to grayscale, then I get :
NO printing ; Cups says "filter failed" ; the printer is no more available, even if I reswitch to "color", UNTIL I switch the printer off then again on..

Let me just add :
- in fact, in the file /usr/share/hplip/data/models/models.dat, you can see plugin=0 and I think that the error is here too,
- I added the quotation marks to "correction", because it looks as if the programming and naming rules are really too loose
(where ? I don't know) : why did the naming and characteristics of this printer change ? And when changed, was there any test made?
And as I see, it is not the only printer to suffer...

So, thanks for any new correction.

Question information

Language:
English Edit question
Status:
Answered
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Whiteboard:
Moving this question to HPLIP project, since it doesn't seem to be related to Launchpad.
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Ahronovitz (lanatol) said : 		#2

Hello,
> Your question #694528 on HPLIP changed:
> https://answers.launchpad.net/hplip/+question/694528
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
 Ok ; may be I misunderstood, but I received an email from launchpad about
two weeks ago, saying that the question moved to HPLIP as it concerned
rather HPLIP
than launchpad.
Since then I have found a solution to my problem, so I added this
solution to

https://bugs.launchpad.net/hplip/+bug/1907444

Here is the solution working for me if it can help, and  as described in
the previous link  :

----------------------------------------------------------------------------------------------

Hello,
I think I got THE complete solution, at least to my own problem,
consisting of the following two steps :

a. Do the suggested "correction" repeated and quoted here :

//one possible fix is to edit /usr/share/hplip/data/models/ and alter
[hp_laserjet_cp1025] to [hp_laserjet_cp_1025].//

Precisely, edit the file /usr/share/hplip/data/models/models.dat and
make the follwing change :

#[hp_laserjet_cp1025]
[hp_laserjet_cp_1025]

I left commented out the first line, just to remember it.

b.PUT OFF THE PRINTER AND THEN PUT IT ON. This should be the rule
whatever you are changing :
if you unplug and replug the usb cable, don't forget to put off and then
put on the printer. If you change anything with cups, with hp-toolbox or
hp-setup don't forget... In fact, I believe that the printer sends some
elements when plugged on, so it is recognized. I don't have any
technical guide, but now, it works. And also, put off the printer before
starting or restarting the computer. Wait until it comes up and put the
printer on afterwards.

Finally, I didn't change my mind about the porgramming and naming rules
(I still don't know where...) leading to the "coorection" point a...
Keep cool, the printer works, until the next misfortune.

-----------------------------------------------------------------------------------------------------

Thanks,

E. Ahronovitz

Revision history for this message
shivani mandora (shivani1708) said : 		#3

Hi ,

Thanks for pointing this issue.

We will include this change in model name in models.dat in our next release.

Can you help with this problem?

Provide an answer of your own, or ask Ahronovitz for more information if necessary.

To post a message you must log in.