ROSA Linux Bugzilla – Bug 635
2012lts printer install bad driver hp 1220
Last modified: 2015-06-22 13:36:31 MSD
Description of problem:
switch on the printer
system asks to you if you want to install some packets
the install runs
at the end you have a notification for printing a test page
go to drakprinter
go to the properties of the printer
you see the driver is "hp-1220,pcl3, hpcups"
this is the wrong driver
my hp 1220 is a postcript one
my printer got the postscipt extension and the memory extension
more : with postscript extension driver i can set the memory extension
with Mageia 2
no pb the good postscript driver is installed
Can you try to install an updated hplip package? It is not in the repos yet, but can be taken from here:
Well, updated hplip is now available in repositories. Would be nice to know if it helps to resolve this bug...
Ok, after updating hplip to 3.12.6, "HP LaserJet 1220 Postscript" driver appears among available drivers for this printer and it will be selected by default when configuring printer for the first time.
sorry but it is false
i made a test with rosa marathon rp1 64 bit and hplip 3.12.6 the last one
the selected driver is always the pcl one not the ppd one
the ppd is in hplip since almost the very beginning of hplip
it was installed by default without pb with mandriva 2008
it's not a hplip pb it's pb upper in system-config-printer
since 2009.0 the setup of the hp 1220 is broken
if you delete the printer installed in system-config-printer
you use hp device manager to install the printer then a good ppd is installed
i assume there is something in cfp that force the use of pcl driver
- unable to print with pcl or ppd one if i use cfg
i found :
-the uri used by hp device manger is :
- the uri used by cfg is
Need restesting before releasing Enterprise X2.
Is it possible to check if this bug is valid for ROSA Desktop Fresh R5?
Let's join this with bug 2720, since we unlikely will care of it for Marathon, and for RED X2 we use Desktop Fresh as a basis.
*** This bug has been marked as a duplicate of bug 2720 ***