driver no longer working

Bug #62883 reported by Jürgen
2
Affects Status Importance Assigned to Milestone
foomatic-db (Ubuntu)
Invalid
Low
Unassigned
gutenprint (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: cupsys-driver-gutenprint

I have an 18 year old HPIIP that I could install without problems. Having installed the latest Dapper updates my printer produces only garbage. Changing the driver to HPII part of the page comes out readable but still not usable.

The problem started with 5.0.0-rc2-0ubuntu6

maybe someone cleaned up "old" drivers and left only one driver for HPII and maybe HPIIP should read HPIIIP because I couldn't find this driver anymore.

Since only a few people work with such old hardware I consider the problem has only low priority, still it is anoying if a Dapper-Dapper update scrambles a working system.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you download the beta version of Edgy/6.10, boot the live CD and try to print from that session? This CD contains the final Gutenprint 5.0.0.

Changed in gutenprint:
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Jürgen (j-w-ott) wrote : Re: [Bug 62883] Re: driver no longer working

Am Freitag, 29. September 2006 11:30 schrieb Till Kamppeter:
> Can you download the beta version of Edgy/6.10, boot the live CD and try
> to print from that session? This CD contains the final Gutenprint 5.0.0.
>
>
> ** Changed in: gutenprint (Ubuntu)
> Importance: Undecided => Low
> Status: Unconfirmed => Needs Info

While testing I had a hardware failure trying to solve it I've fried my K7.

Back now with AMD 2X :-)

Finishing the test the recommended hp laserjet 2p works like it used to with
edgy.

(My dapper has two choices for the same printer hp laserjet IIp and hp
laserjet 2p, only IIp can be installed 2p gives an error messages)

Thanks for the quick response !!

Jürgen

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Thank you for your info about the LaserJet 2P/IIP.

Can you post the output of

cat /proc/sys/dev/parport/parport*/autoprobe*

This will help me to remove the IIP/2P confusion from the Foomatic database.

So the Gutenprint bug is fixed. I will close it.

Changed in gutenprint:
status: Needs Info → Fix Released
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Will make one out of the two LaserJet 2P/IIP entries in the Foomatic database, name will depend on the auto-detection info.

Jürgen, if you do not get output from the command I have given you in the previous comment, please tell me what name is written on the printer: LaserJet 2P or LaserJet IIP?

Changed in foomatic-db:
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Jürgen (j-w-ott) wrote :

Am Tuesday, 3. October 2006 09:46 schrieb Till Kamppeter:
Hi

all autoprobe entries are empty. I remember that the autoprobe feature was
introduced shortly after the IIP.

Using the name 2p is better because the printer gets sorted at the beginning
of the laserjet list which makes sense because all the later models should
also work with this driver.

On the othe hand the printer name reads IIP in the documention and on the
printer case.

Regards

Jürgen

> Will make one out of the two LaserJet 2P/IIP entries in the Foomatic
> database, name will depend on the auto-detection info.
>
> Jürgen, if you do not get output from the command I have given you in
> the previous comment, please tell me what name is written on the
> printer: LaserJet 2P or LaserJet IIP?
>
>
> ** Changed in: foomatic-db (Ubuntu)
> Importance: Undecided => Low
> Status: Unconfirmed => Needs Info

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Thank you very much. I will fix this in foomatic-db.

Changed in foomatic-db:
status: Needs Info → In Progress
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Neither in the Foomatic database nor on the current Edgy (gnome-cups-manager, "lpinfo -m") I see any "HP LaserJet II" or "HP LaserJet III" entry, always "HP LaserJet 2" or "HP LaserJet 3". So there is no bug in foomatic-db to fix. Either it is already fixed (must be years ago, I do not remember when and whether I have fixed it) or the "HP LaserJet II" entries come from another package, which is either fixed or not installed by you.

Does your Edgy list an "HP LaserJet II" or "HP LaserJet III" entry? What is the output of "dpkg -l '*ppd*'" on your machine?

Closing this for foomatic-db.

Changed in foomatic-db:
status: In Progress → Rejected
Revision history for this message
Jürgen (j-w-ott) wrote :
Download full text (10.2 KiB)

Hello,

there is something strange happening since printing is working again ! I tried different printers
and restarted cupsys and it didn´t work. After a restart of the computer the next day someone printed a page (I didn´t try anymore)
and suddenly the page came out.

Well I changed the motherboard and the CPU and the memory meanwhile, but I don´t think it was a hardware problem since Excel
would print out of wine.

enclosed you can find the requested output

jott@aldi:~$ dpkg -l *ppd*
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Säubern/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/Fehlgeschl. Konf./Halb install.
|/ Fehler?=(keiner)/Halten/R=Neuinst. notw/X=beides (Status, Fehler: GROß=schlecht)
||/ Name Version Beschreibung
+++-==================-==================-====================================================
un cupsomatic-ppd <keine> (keine Beschreibung vorhanden)
pn foomatic-filters-p <keine> (keine Beschreibung vorhanden)
ii hplip-ppds 0.9.7-4ubuntu1 HP Linux Printing and Imaging - PPD files
un pppdcapiplugin <keine> (keine Beschreibung vorhanden)
jott@aldi:~$

This is the list I see using the cups frontend

"hpijs/HP/HP-DeskJet_9800-hpijs.ppd" >HP DeskJet 9800 Foomatic/hpijs (recommended) - HPLIP 0.9.7 (en)
"cups-included/HP/deskjet.ppd" >HP DeskJet Series CUPS v1.2 (en)
"hpijs/HP/HP-e-printer_e20-hpijs.ppd" >HP e-printer e20 Foomatic/hpijs (recommended) - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4-hpijs.ppd" >HP LaserJet 4 Foomatic/hpijs (recommended) - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4_Plus-hpijs.ppd" >HP LaserJet 4 Plus Foomatic/hpijs - HPLIP 0.9.7 (en)
"gutenprint/5.0/en/stp-pcl-4.5.0.ppd.gz" >HP LaserJet 4 series - CUPS+Gutenprint v5.0.0-rc2 (en)
"gutenprint/5.0/en/stp-pcl-4l.5.0.ppd.gz" >HP LaserJet 4L - CUPS+Gutenprint v5.0.0-rc2 (en)
"hpijs/HP/HP-LaserJet_4L-hpijs.ppd" >HP LaserJet 4L Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4M-hpijs.ppd" >HP LaserJet 4M Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4ML-hpijs.ppd" >HP LaserJet 4ML Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4P-hpijs.ppd" >HP LaserJet 4P Foomatic/hpijs (recommended) - HPLIP 0.9.7 (en)
"gutenprint/5.0/en/stp-pcl-4si.5.0.ppd.gz" >HP LaserJet 4Si - CUPS+Gutenprint v5.0.0-rc2 (en)
"hpijs/HP/HP-LaserJet_4Si-hpijs.ppd" >HP LaserJet 4Si Foomatic/hpijs - HPLIP 0.9.7 (en)
"gutenprint/5.0/en/stp-pcl-4v.5.0.ppd.gz" >HP LaserJet 4V - CUPS+Gutenprint v5.0.0-rc2 (en)
"hpijs/HP/HP-LaserJet_4V-hpijs.ppd" >HP LaserJet 4V Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_4V_4LJ_Pro-hpijs.ppd" >HP LaserJet 4V/4LJ Pro Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_5-hpijs.ppd" >HP LaserJet 5 Foomatic/hpijs (recommended) - HPLIP 0.9.7 (en)
"gutenprint/5.0/en/stp-pcl-5.5.0.ppd.gz" >HP LaserJet 5 series - CUPS+Gutenprint v5.0.0-rc2 (en)
"hpijs/HP/HP-LaserJet_5L-hpijs.ppd" >HP LaserJet 5L Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_5M-hpijs.ppd" >HP LaserJet 5M Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_5MP-hpijs.ppd" >HP LaserJet 5MP Foomatic/hpijs - HPLIP 0.9.7 (en)
"hpijs/HP/HP-LaserJet_5P-hpijs....

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.