[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed



Hello Till,
On Sun, Mar 11, 2012 at 11:45:40AM +0100, Till Kamppeter wrote:
> Note that the new PPD I suggested does not use foomatic-rip, it
> should work (or not work) independent of the foomatic-filters version
> installed.

Ok. (I somehow get the feeling that foomatic-filters is also not the
entire picture, but for me this is hard to pin down, so thank you once
more for your extensive help).

So I now emptied all queues (using the web interface). Shut down the
printer. Stopped cups. Upgraded to the latest version of
foomatic-filters.

Start cups. Turn on printer again.

> The piece of error_log you pasted showed only some USB timeouts.
> Whether they actually prevent your printer from printing is not
> known.

Ok.

> To determine whether valid PostScript data reaches the backend, you
> need to clone your print queues into queues pointing into a file.
> 
> Run the command
> 
> cupsctl FileDevice=yes

Done.

> then do for each print queue:

Pasted form the CUPS web interface:
↓ Queue Name ↓  Beschreibung    Ort     Marke und Modell        Status
FS-1020D        Kyocera FS-1020D        sneo    Kyocera FS-1020D Foomatic/Postscript    Frei
Kyocera-FS-1020D-Postscript-Kyocera     Kyocera FS-1020D - Test Testdrucker     Kyocera Mita FS-1020D   Frei
Kyocera_FS-1020D        Kyocera FS-1020D        Drucker auf dem Schreibtisch    Kyocera Mita FS-1020D   Frei

> lpadmin -p <queue>-file -E -v file:/tmp/printout-<queue> -P
> /etc/cups/ppd/<queue>.ppd
> 
> Replacs <queue> by the actual queue name.

for i in FS-1020D Kyocera-FS-1020D-Postscript-Kyocera Kyocera_FS-1020D; do lpadmin -p ${i}-file -E -v file:/tmp/printout-${i} -P /etc/cups/ppd/${i}.ppd; done

> Print into the clone queues, always the same input file, a file which
> showed the problem for you.

Ok, used evince, which clearly saw the new queues, the same pdf file
into every queue.

> Make the resulting files readable for normal users:
> 
> chmod 777 /tmp/printout*

Done. 
-rwxrwxrwx 1 root  root  196960 Mär 11 19:04 /tmp/printout-FS-1020D
-rwxrwxrwx 1 root  root  199338 Mär 11 19:04 /tmp/printout-Kyocera_FS-1020D
-rwxrwxrwx 1 root  root  199270 Mär 11 19:04 /tmp/printout-Kyocera-FS-1020D-Postscript-Kyocera

/tmp/printout-FS-1020D:                            PostScript document text conforming DSC level 3.0, Level 2

Looks fine (using evince), evince throws lots of 
GPL Ghostscript 9.05: Error: Font Renderer Plugin ( FreeType ) return code = -1


/tmp/printout-Kyocera_FS-1020D:                    PJL encapsulated PostScript document text
/tmp/printout-Kyocera-FS-1020D-Postscript-Kyocera: PJL encapsulated PostScript document text

Looks fine, altough I have to press Page Down one time more than the
document should have pages (there are no page numbers shown).


> Examine the files to see whether they contain valid PostScript, have
> PJL commands in the beginning, ... Note that if they have PJL
> commands in the beginning, evince cannot display their PostScript
> part on the screen but gv can.
> 
> Are the files OK or are they already without printable data?

The look ok.

> If they contain printable data, print them unfiltered to the original
> queues:
> 
> lpr -P <queue> -oraw /tmp/printout-<queue>

lpr -P FS-1020D -oraw /tmp/printout-FS-1020D
Printer powers up (as if it were to print). No output, unfortunately.
The CUPS web front end does not show the job neither.

lpr -P Kyocera_FS-1020D -oraw /tmp/printout-Kyocera_FS-1020D
No reaction from the printer. But the job does show up in the web
frontend of CUPS as active job. 


lpr -P Kyocera-FS-1020D-Postscript-Kyocera -oraw /tmp/printout-Kyocera-FS-1020D-Postscript-Kyocera

Same as previous, no reaction from printer, the job does show up in
the CUPS web frontend *and*
the first job is now shown as "unerledigt seit" (not done since) with
the reason "/usr/lib/cups/backend/usb failed"

For a change, lpstat for root (who started the jobs) now shows them as
well:
root@sneo:~# lpstat
Kyocera_FS-1020D-251    root            199680   So 11 Mär 2012 19:14:38 CET
Kyocera-FS-1020D-Postscript-Kyocera-252 root            199680   So 11 Mär 2012 19:16:22 CET

> For the foomatic-filters case (Foomatic/Postscript queue), do this
> with both the old and the new foomatic-filters with the same input
> file and attach the /tmp/printout-<queue>  files once the one which
> prints of the old foomatic-filters and second, the one which does not
> print of the new foomatic-filters.

I'm not sure I'm following you here entirely, I assume that you mean
the queue "FS-1020D" which contains the string foomatic (and its -file
counterpart, of course).

So shutting down cups and the printer. Downgrading foomatic-filters,
starting cups again. Kill the pending jobs in the web frontend of
cups. Turn on printer again.

mv -iv printout-FS-1020D printout-FS-1020D.newFoomatic

Printing on the real queue works, output looks fine.

Printing on the file queue provides a different file:
-rw------- 1 root  root  165670 Mär 11 19:28 /tmp/printout-FS-1020D
-rwxrwxrwx 1 root  root  196960 Mär 11 19:04 /tmp/printout-FS-1020D.newFoomatic

root@sneo:/tmp# diff -u /tmp/printout-FS-1020D /tmp/printout-FS-1020D.newFoomatic | head -n 30
--- /tmp/printout-FS-1020D      2012-03-11 19:28:12.000000000 +0100
+++ /tmp/printout-FS-1020D.newFoomatic  2012-03-11 19:04:25.000000000 +0100
@@ -1,2577 +1,2533 @@
 %!PS-Adobe-3.0
-%%LanguageLevel: 2
-%%DocumentSuppliedResources: (atend)
-%%DocumentMedia: plain 595 842 0 () ()
 %%BoundingBox: 0 0 595 842
+%%Creator: GPL Ghostscript 905 (ps2write)
+%%LanguageLevel: 2
+%%CreationDate: D:20120311190424+01'00'
 %%Pages: 2
 %%EndComments
 %%BeginProlog
-%%BeginDefaults
-%%PageMedia: plain
-%%EndDefaults
-%%BeginProlog
-%%BeginResource: procset xpdf 3.00 0
-%%Copyright: Copyright 1996-2004 Glyph & Cog, LLC
-/xpdf 75 dict def xpdf begin
-% PDF special state
-/pdfDictSize 15 def
-/pdfSetup {
-  3 1 roll 2 array astore
-  /setpagedevice where {
-    pop 3 dict begin
-      /PageSize exch def
-      /ImagingBBox null def
-      /Policies 1 dict dup begin /PageSize 3 def end def

I'll provide the two files in a seperate e-mail (off bug) for debugging
(please limit the file to those debugging and remove it afterwards, if
possible, I should have taken a more innocent file, sorry.

Thanks again for your help.

Greetings

         Helge

> On 03/11/2012 10:32 AM, Helge Kreutzmann wrote:
> >On Fri, Mar 09, 2012 at 08:05:20PM +0100, Till Kamppeter wrote:
> >>Please set up a print queue with this PPD:
> >>
> >>http://www.openprinting.org/ppd-o-matic.php?driver=Postscript-Kyocera&printer=Kyocera-FS-1020D
> >
> >Did so. The PPD seems to be the English version of one I already have
> >installed (a Diff confirms this, only some "terms" are translated).
> >
> >>Can you print then?
> >
> >No, not with current foomatic-filters:
> >
> >ii  foomatic-filters                             4.0.12-1                                     OpenPrinting printer support - filters
> >
> >Error log excerpt (lpstat of that user is still showing the job, btw.,
> >lpq does not show anything):
> >D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 POST / HTTP/1.1
> >D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Active clients, printing jobs, and dirty files", busy="Printing jobs and dirty files"
> >D [11/Mar/2012:10:05:06 +0100] cupsdAuthorize: No authentication data provided.
> >D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1
> >D [11/Mar/2012:10:05:06 +0100] Get-Jobs ipp://localhost/
> >D [11/Mar/2012:10:05:06 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost
> >D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Active clients, printing jobs, and dirty files"
> >D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 WAITING Closing on EOF
> >D [11/Mar/2012:10:05:06 +0100] cupsdCloseClient: 16
> >D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
> >I [11/Mar/2012:10:05:09 +0100] Saving job.cache...
> >D [11/Mar/2012:10:05:09 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs and dirty files"
> >D [11/Mar/2012:10:05:15 +0100] [Job 237] Wrote 8192 bytes of print data...
> >D [11/Mar/2012:10:05:15 +0100] [Job 237] Read 8192 bytes of print data...
> >D [11/Mar/2012:10:05:23 +0100] cupsdAcceptClient: 16 from localhost (Domain)
> >D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 POST / HTTP/1.1
> >D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Active clients and printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:05:23 +0100] cupsdAuthorize: No authentication data provided.
> >D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1
> >D [11/Mar/2012:10:05:23 +0100] Get-Jobs ipp://localhost/
> >D [11/Mar/2012:10:05:23 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost
> >D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs"
> >D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 WAITING Closing on EOF
> >D [11/Mar/2012:10:05:23 +0100] cupsdCloseClient: 16
> >D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:05:26 +0100] cupsdAcceptClient: 16 from localhost (Domain)
> >D [11/Mar/2012:10:05:26 +0100] cupsdReadClient: 16 POST / HTTP/1.1
> >D [11/Mar/2012:10:05:26 +0100] cupsdSetBusyState: newbusy="Active clients and printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:05:26 +0100] cupsdAuthorize: No authentication data provided.
> >D [11/Mar/2012:10:05:26 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1
> >D [11/Mar/2012:10:05:26 +0100] Get-Jobs ipp://localhost/
> >D [11/Mar/2012:10:05:26 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost
> >D [11/Mar/2012:10:05:26 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs"
> >D [11/Mar/2012:10:05:26 +0100] cupsdReadClient: 16 WAITING Closing on EOF
> >D [11/Mar/2012:10:05:26 +0100] cupsdCloseClient: 16
> >D [11/Mar/2012:10:05:26 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:05:30 +0100] cupsdAcceptClient: 16 from localhost (Domain)
> >D [11/Mar/2012:10:05:30 +0100] cupsdReadClient: 16 POST / HTTP/1.1
> >D [11/Mar/2012:10:05:30 +0100] cupsdSetBusyState: newbusy="Active clients and printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:05:30 +0100] cupsdAuthorize: No authentication data provided.
> >D [11/Mar/2012:10:05:30 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1
> >D [11/Mar/2012:10:05:30 +0100] Get-Jobs ipp://localhost/
> >D [11/Mar/2012:10:05:30 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost
> >D [11/Mar/2012:10:05:30 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs"
> >D [11/Mar/2012:10:05:30 +0100] cupsdReadClient: 16 WAITING Closing on EOF
> >D [11/Mar/2012:10:05:30 +0100] cupsdCloseClient: 16
> >D [11/Mar/2012:10:05:30 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs"
> >D [11/Mar/2012:10:06:15 +0100] [Job 237] Got USB transaction timeout during write
> >D [11/Mar/2012:10:06:15 +0100] [Job 237] Wrote 7936 bytes of print data...
> >D [11/Mar/2012:10:06:15 +0100] Report: clients=0
> >D [11/Mar/2012:10:06:15 +0100] Report: jobs=4
> >D [11/Mar/2012:10:06:15 +0100] Report: jobs-active=1
> >D [11/Mar/2012:10:06:15 +0100] Report: printers=3
> >D [11/Mar/2012:10:06:15 +0100] Report: printers-implicit=0
> >D [11/Mar/2012:10:06:15 +0100] Report: stringpool-string-count=17429
> >D [11/Mar/2012:10:06:15 +0100] Report: stringpool-alloc-bytes=12320
> >D [11/Mar/2012:10:06:15 +0100] Report: stringpool-total-bytes=314784
> >D [11/Mar/2012:10:06:17 +0100] [Job 237] Wrote 256 bytes of print data...
> >D [11/Mar/2012:10:06:17 +0100] [Job 237] Read 8192 bytes of print data...
> >D [11/Mar/2012:10:07:17 +0100] [Job 237] Got USB transaction timeout during write
> >D [11/Mar/2012:10:07:17 +0100] [Job 237] Wrote 7936 bytes of print data...
> >D [11/Mar/2012:10:07:17 +0100] Report: clients=0
> >D [11/Mar/2012:10:07:17 +0100] Report: jobs=4
> >D [11/Mar/2012:10:07:17 +0100] Report: jobs-active=1
> >D [11/Mar/2012:10:07:17 +0100] Report: printers=3
> >D [11/Mar/2012:10:07:17 +0100] Report: printers-implicit=0
> >D [11/Mar/2012:10:07:17 +0100] Report: stringpool-string-count=17429
> >D [11/Mar/2012:10:07:17 +0100] Report: stringpool-alloc-bytes=12320
> >D [11/Mar/2012:10:07:17 +0100] Report: stringpool-total-bytes=314784
> >D [11/Mar/2012:10:07:18 +0100] [Job 237] Wrote 256 bytes of print data...
> >D [11/Mar/2012:10:07:18 +0100] [Job 237] Read 8192 bytes of print data...
> >
> >Going back to 4.0.9-1 and restarting cups, and printing again on that
> >printer, also no output :-((
> >
> >Switching printer off, restarting cups and turning printer back on
> >(still with 4.0.9-1) and starting the print job a third time als no
> >print out on that printer, also printing on other queues does only
> >queue the jobs (according to lpstat, lpq does not show any output at
> >all).
> >
> >Restarting cups again.
> >
> >In /var/cache/cups I see
> >-rw-r--r-- 1 root root     7155 Mär 11 09:46 Kyocera-FS-1020D-Postscript-Kyocera.data
> >-rw-r----- 1 root lp       1023 Mär 11 10:22 job.cache.O
> >-rw-r----- 1 root lp       1023 Mär 11 10:23 job.cache
> >
> >And lpstat of the user (only that user!) still show the three
> >submitted jobs.
> >
> >I'm a bit lost, so far I got back to a printing state by downgrade and
> >restart...
> >
> >And it's not easy to see whats going on when command like lpq only
> >display two or three blank lines, even though jobs are pending, and
> >"-a" or "-l" does not yield any output either.
> >
> >Thanks for taking care!
> >
> >Greetings
> >
> >            Helge
> 

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


Reply to: