> Date: Sat, 7 Sep 2013 00:44:50 -0700 (PDT) > From: Sirsendu Roy <xai...@yahoo.com> > To: BLFS Support List <blfs-support@linuxfromscratch.org> > Subject: Re: [blfs-support] Cannot Print document using HP Printer > > Hello, > Here is the out of : > $ lpstat -t -v > > scheduler is running > no system default destination
Side-note: at some point, you'll likely want to define a default printer; an easy way to do this is via the cups web-admin interface http://localhost:631/ (or http://127.0.0.1:631/ , etc). > device for Deskjet_1050_J410: > hp:/usb/Deskjet_1050_J410_series?serial=CN16E12K6G05QT > Deskjet_1050_J410 accepting requests since Sa 07 Sep 2013 09:09:52 CEST > printer Deskjet_1050_J410 is idle. enabled since Sa 07 Sep 2013 09:09:52 CEST > Can't feed job data into Ghostscript The overall printing structure is approximately and basically (am not assuming you don't already know this - just mention it in case of use): --- * your software is likely creating print-jobs in postscript language or similar. * your printer, being a Deskjet, very likely does not understand postscript &c directly: i.e. your printer doesn't have a postscript interpreter built-in to it; the printer likely only understands 'PCL' language directly. * therefore something needs to translate between postscript and the-printer's-native-language. One 'translator' that will do that (using some auxiliary help) is Ghostscript. --- As said, I don't know enough about hplip in detail and how it fits in. But from what Pierre says (IIUIC) in another reply, hplip doesn't provide a postscript translator, or at the very least not a good enough one. > Deskjet_1050_J410-13 roy 4226048 Sa 24 Aug 2013 12:27:28 CEST > Deskjet_1050_J410-16 roy 7168 Sa 07 Sep 2013 09:09:18 CEST > device for Deskjet_1050_J410: > hp:/usb/Deskjet_1050_J410_series?serial=CN16E12K6G05QT > These queue items, along with the 'can't feed data' message above, might be what the 'dirty files' messages below are referring to. While debugging, you might want to clear (i.e. remove) those messages from the print queue, so that you're debugging from a reasonably 'clean' known state. As a sanity-check, can you login to the cups web-admin as root, and from within that web-admin interface, do: -- * set the printer to be the default. * clear-out the print queue(s). * do a test-print. -- And look at what the error log is saying during those actions. NB to do it as root in this first instance. Don't yet try to do it as user 'roy' or other non-root user: that stuff can follow once you can print as root; otherwise, you might be inadvertently trying to debug permissions issues as well as driver/filter/&c issues as well as perhaps other issues, while not (yet) realising that you're seeing multiple levels of problems. > > here is also the output of the error_log file : > > > D [07/Sep/2013:08:59:13 +0200] cupsdSetBusyState: newbusy="Dirty files", > busy="Active clients and dirty files" > D [07/Sep/2013:08:59:13 +0200] [Client 16] POST / HTTP/1.1 > D [07/Sep/2013:08:59:13 +0200] cupsdSetBusyState: newbusy="Active clients and > dirty files", busy="Dirty files" > D [07/Sep/2013:08:59:13 +0200] [Client 16] No authentication data provided. > D [07/Sep/2013:08:59:13 +0200] [Client 16] 2.0 CUPS-Get-Printers 3 > D [07/Sep/2013:08:59:13 +0200] CUPS-Get-Printers > D [07/Sep/2013:08:59:13 +0200] Returning IPP successful-ok for > CUPS-Get-Printers (no URI) from localhost > D [07/Sep/2013:08:59:13 +0200] cupsdSetBusyState: newbusy="Dirty files", > busy="Active clients and dirty files" > D [07/Sep/2013:08:59:13 +0200] [Client 16] HTTP_WAITING Closing on EOF > D [07/Sep/2013:08:59:13 +0200] [Client 16] Closing connection. > Ref comments above re the 'dirty files'. > And when I am seeing the job stat like this : > Deskjet_1050_J410-13 Unknown Withheld 4127k Unknown stopped "write > failed: Interrupted system call" > The same error as previuosly described. I am a member of the lpadmin group. Yes, the errmsg could be just a pipe failing, re 'can't feed data in Ghostscript'. Re lpadmin group: ref comments above on trying those things as root, and getting printing to work here as root, before trying as ordinary user. > > What I didn't do till now is to install the ghostscript. But If I have a > physical printer do I still need a ghost script? > See above note re structure/sequence for why you probably do, in practice, 'need' ghostscript or similar for the type of printer that you are using. hth, akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
