Created attachment 347748 [details] cups access log Description of problem: I logged in as an ordinary user, started System->Administration->Printing and added a new printer. My HP DeskJet 815C was correctly found but the test page is forever queued. Also any other document I wish to print is stuck in the queue. Version-Release number of selected component (if applicable): cups-1.4-0.b2.18.fc11.i586 How reproducible: Always. Steps to Reproduce: 1. System->Administration->Printing 2. Add HP DeskJet 815C 3. Try to print the test page Actual results: Page queued forever. Expected results: Page printed. Additional info: I'm attaching access_log and error_log after such an attempt.
Created attachment 347749 [details] cups error log
Please edit /etc/foomatic/filter.conf and add this line to the end: debug: 1 Then print a test page again. You should now have two files /tmp/foomatic-rip.ps and /tmp/foomatic-rip.log -- please attach them here. Afterwards you can change filter.conf so that it no longer has 'debug: 1' in it.
i had similar symptoms with my brother 5250dn. the problem seems to be i configured it as a network printer (with an ip). the above trick (debug: 1) never worked but, removing the printer and configuring as jet direct worked. one problem is i had to choose the driver by hand, by default it was identified as "generic printer". now i'll dig deeper with my office brother 1430 wich no longer works after installing f11. this is usb connected so the only thing i can think off, is that the driver is wrong.
(In reply to comment #3) > i had similar symptoms with my brother 5250dn. Please report them in a separate bug report. Printing problems can very often appear to be the same but have different root causes. What we currently know about this particular problem is that the foomatic-rip filter is failing with exit status 3, which is why I'm requesting debugging information from foomatic.
done. https://bugzilla.redhat.com/show_bug.cgi?id=506708
and https://bugzilla.redhat.com/show_bug.cgi?id=506803
Created attachment 349695 [details] foomatic rip log
Created attachment 349696 [details] foomatic rip ps
It seems as though the hpijs driver is unable to understand the device ID the printer gives. Please attach the output from this command, run as root when the printer is powered and connected: /usr/sbin/lpinfo -l --include-schemes=usb -v
Created attachment 354160 [details] lpinfo output Hi, it produces no output at all: root@localhost:~# /etc/init.d/cups status cupsd (pid 2352) is running... root@localhost:~# /usr/sbin/lpinfo -l --include-schemes=usb -v root@localhost:~# But this is not a USB printer.. I'm attaching the output from: /usr/sbin/lpinfo -l -v Thanks.
Thanks, and sorry for the incorrect assumption. Fishing out the Device ID, we get this: MFG:HEWLETT-PACKARD; MDL:DESKJET 815C; CMD:MLC,PCL,PML; CLASS:PRINTER; DESCRIPTION:Hewlett-Packard DeskJet 815C; SERN:ES97E141WQIE; VSTATUS:$HB0$FC0,ff,DN,IDLE,CUT; Needs further investigation into hpijs source code to see why it has a problem with that.
Looks like you are using the wrong PPD for this printer. What does 'rpm -q system-config-printer' say? Please delete the queue and re-add it. Does printing work now? If not, please attach the PPD file which has been set for the printer (from the /etc/cups/ppd/ directory). Thanks.
Hi, root@localhost:~# rpm -q system-config-printer system-config-printer-1.1.7-4.fc11.i586 The PPD file was for 910 (not for my 815C). Just in case, I'll attach the PPD file. After manually browsing for 815C from the list printing works now. If wanted, I could purge all my configs and try to figure out where did this wrong PPD file came up. Thanks.
Created attachment 355446 [details] Default PPD for 815C (not working)
(In reply to comment #13) > If wanted, I could purge all my configs and try to figure out where did this > wrong PPD file came up. Yes please. I think that's the root of the problem.
> If wanted, I could purge all my configs and try to figure out where did this > wrong PPD file came up. I was unable to reproduce this anymore so it might have been a local hickup or some update has fixed this already since the initial report. Sorry for the noise and thanks a lot for your help!