[gutsy] HP DJ F380 ejecting blank pages

Please provide the information described here: https://wiki.ubuntu.com/DebuggingPrintingProblems.
Don't forget to attach the output of the printingbug info script and your cups error_log.

kelner@luther:~$ tail -f /var/log/messages
Sep 12 01:07:49 luther kernel: [ 105.718389] usb 1-1: configuration #1 chosen from 1 choice
Sep 12 01:07:49 luther kernel: [ 106.319438] Bluetooth: HCI USB driver ver 2.9
Sep 12 01:07:49 luther kernel: [ 106.328431] usbcore: registered new interface driver hci_usb
Sep 12 01:07:50 luther kernel: [ 106.701712] agpgart: Putting AGP V2 device at 0000:00:0b.0 into 4x mode
Sep 12 01:07:50 luther kernel: [ 106.701853] agpgart: Putting AGP V2 device at 0000:00:10.0 into 4x mode
Sep 12 01:07:51 luther kernel: [ 107.458026] [drm] Setting GART location based on new memory map
Sep 12 01:07:51 luther kernel: [ 107.458041] [drm] Loading R200 Microcode
Sep 12 01:07:51 luther kernel: [ 107.458095] [drm] writeback test succeeded in 1 usecs
Sep 12 01:11:16 luther kernel: [ 312.847402] usb 3-1: USB disconnect, address 2
Sep 12 01:11:16 luther kernel: [ 312.847802] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: removed
Sep 12 01:11:44 luther kernel: [ 341.195270] usb 3-1: new full speed USB device using ohci_hcd and address 3
Sep 12 01:11:45 luther kernel: [ 341.419745] usb 3-1: configuration #1 chosen from 1 choice
Sep 12 01:11:45 luther kernel: [ 341.428611] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5511

kelner@luther:~$ lpinfo -v
network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_printer_CN6ADGG13Q04KH
direct usb://HP/Deskjet%20F300%20series?serial=CN6ADGG13Q04KH
direct hpfax
direct hp
network http
network ipp
network lpd
file cups-pdf:/
direct scsi
network smb

Your printer queue should be configured to use the hp backend, but it looks like the HP backend doesn't detect your printer.

Can you attach the output of the following commands:
$ ls -l /usr/lib/cups/backend*
$ /usr/lib/cups/backend/hp

kelner@luther:~$ /usr/lib/cups/backend/hp
direct hp:/usb/Deskjet_F300_series?serial=CN6ADGG13Q04KH "HP Deskjet F300 series" "HP Deskjet F300 series USB CN6ADGG13Q04KH HPLIP" "MFG:HP;MDL:Deskjet F300 series;CLS:PRINTER;DES:Deskjet F300 series;SN:CN6ADGG13Q04KH;"

Can you remove your print queue, update your Gutsy to the current state and then turn off and turn on the printer? Then your printer should get set up correctly. See the notifications popping up on your GNOME panel.

It indeed does get set up, but symptoms are the same - printer ejects blank pages.

Does your printer work when manually setting up a printer queue with the hplip backend (hp:/usb/Deskjet_F300_series?serial=CN6ADGG13Q04KH)?

It gets even worse. The test page sits in the queue forever, I get this in /var/log/syslog:
Sep 27 20:24:42 luther Deskjet_F300_series?serial=CN6ADGG13Q04KH: io/hpmud/musb.c 549: invalid product id string: Operation not permitted
Sep 27 20:24:42 luther Deskjet_F300_series?serial=CN6ADGG13Q04KH: io/hpmud/musb.c 1003: unable to open hp:/usb/Deskjet_F300_series?serial=CN6ADGG13Q04KH
Sep 27 20:24:42 luther Deskjet_F300_series?serial=CN6ADGG13Q04KH: INFO: open device failed; will retry in 30 seconds...

Right now printing with hp:// backend gives the same result usb:// backend does.

What do you mean? Does it print correctly now with the the hp:/ backend?

It means that printers just ejects requested amount of blank pages, i.e. when I print n-pages, I get n blank pages.

I'm too trigger happy and clicked the wrong button. hp:/ backend results in the same bug that I desribed in the bug report

I have the same problem with a fresh Gutsy install on an iBook G4 with a HP-PhotoSmart_7345. The same printer works without problems with Gutsy on a MacBook, however. As Andrzej also had this problem on a powerpc, it might well be specific to that architecture.

I have attached the debug info from DebuggingPrintingProblems, just in case.

I have a similar problem with a HP DeskJet 5652 (which is connected to the local network with a print server). The printer does not always eject blank pages, it simply forgets to print the text.

I no not use a powerpc, so I do not think that the bug is specific to the architecture. For me, the problem occurs both with the i386-version and with the amd64-version of Kubuntu.

I will attach both a scan of the printed CUPS-test page and the output of the printingbuginfo script run on my computer.

My mother's g3 iMac, working fine with Feisty, started printing blank pages exactly as Pascal describes after the update to Gutsy. HP C3180 inkjet/scanner. Will attach appropriate debug stuff next time I have access to the machine.

Dave, Raghu, Don, it seems that HPIJS does not output text (black?) or even any page content in general for a wide range of HP inkjet printers (not all models) in version 2.7.7 and 2.7.10. Can you check and fix this?

To anyone having this problem:

Run the attached scripts (which I will post in order) using this method:

Photosmarts and higher numbered deskjets run inkjet.sh

DeskJet F380 run djf300.sh

Run:

sh inkjet.sh testpage.ps

It produces testpage.pcl, you can then do

Then run:

lpr -o raw -P<queue_name> testpage.pcl

Where "<queue_name>" is the name of the printer queue. You can get this from http://localhost:631/printers or by running hp-check.

Then upload the testpage.pcl so we can take a look at it.

Thanks!

A

Sorry uploading the rest of the files needed for troubleshooting.

Actually it may be a PowerPC problem. My report from October was invalid.

I have three printers and I rarely use Windows. Before I made my comment, I mainly used the two other printers, so I did not realize that the black printing cartridge on the DeskJet had dried out. Shortly after I made the comment, I had to go to the hospital (for about two months). Sorry for being late in correcting my mistake.

As all other reporters seem to use the PowerPC architecture, it may indeed be specific to that architecture.

I have exactly the same problem with a Photosmart A610 on gutsy/powerpc - blank pages spit out for every one I request. I'd set up the printer via the hp-setup tool. If the devs are stuck with this I am happy to provide a root login to my Mac (and availability on IM to confirm what comes out :) ) to investigate.

Aaron, I did this:

zcat /usr/share/hplip/data/ps/testpage.ps.gz >testpage.ps
sh inkjet.sh testpage.ps
lpr -o raw testpage.pcl

and my Mum's HP C3180 ejected a blank page. Gutsy, iMac G3.

Attaching testpage.ps, inkjet.sh and testpage.pcl.

I also did this:

scp inkjet.sh testpage.ps my.x86.gutsy.server:/home/stephen/foo
ssh my.x86.gutsy.server
sudo apt-get update
sudo apt-get install hplip
sudo apt-get install hpijs
cd foo
sh inkjet.sh testpage.ps
logout
scp my.x86.gutsy.server:/home/stephen/foo/testpage.pcl .
lpr -o raw testpage.pcl

and the page printed as it should. The testpage.pcl file generated on x86 Gutsy is also *much* bigger (1039616 bytes) than the one from ppc Gutsy (73401 bytes). I am starting to think that the current ppc hpijs is just horribly broken.

OK, it's not hpijs, it's ghostscript. This rather horrid workaround has Mum printing again:

cd /tmp
wget http://archive.ubuntu.com/ubuntu/pool/main/g/gs-esp/libgs-esp8_8.15.4.dfsg.1-0ubuntu1_powerpc.deb
dpkg -i libgs-esp8_8.15.4.dfsg.1-0ubuntu1_powerpc.deb
wget http://archive.ubuntu.com/ubuntu/pool/main/g/gs-esp/gs-esp_8.15.4.dfsg.1-0ubuntu1_powerpc.deb
dpkg -x gs-esp_8.15.4.dfsg.1-0ubuntu1_powerpc.deb foo
sudo cp -r foo/usr/share/gs-esp /usr/share
sudo mv /usr/bin/gs /usr/bin/gs.broken
sudo cp /tmp/foo/usr/bin/gs-esp /usr/bin/gs

This replaces the Gutsy gs with the same version that was in Feisty, while leaving the package management system none the wiser. Hopefully the next ghostscript upgrade will fix gs rather than breaking it again.

To get printing back to where it was in Feisty (i.e. working), I also had to work around another bug in a similarly rude way:

https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/145278

Hope this helps.

Andrzej Mendel, Flabdablet,

Is this still an issue with the newer ghostscript package in Ubuntu Hardy or Intrepid, the current development version?

It has apparently been fixed by the time Gutsy was released. It works here now.