Comment 72 for bug 1391963

Revision history for this message
In , Tim (tim-redhat-bugs) wrote :

Description of problem:
When trying to convert application/postscript to application/vnd.cups-pdf, the pstotiff filter (from HPLIP for faxing support) gets used:

application/postscript
  -> application/pdf via pstopdf (100)
  -> application/vnd.cups-pdf via pdftopdf (66)
  = 166

application/postscript
  -> image/tiff via pstotiff (80)
  -> application/vnd.cups-pdf via imagetopdf (33)
  = 113

So the pstotiff path wins.

CUPS Raster drivers such as gutenprint seem to be unaffected:

application/postscript
  -> application/vnd.cups-postscript via pstops (66)
  -> application/vnd.cups-raster via gstoraster (100)
  = 166

application/postscript
  -> image/tiff via pstotiff (80)
  -> application/vnd.cups-raster via imagetoraster (100)
  = 180

Version-Release number of selected component (if applicable):
cups-filters-1.0.35-3.fc19.x86_64
hplip-3.13.7-1.fc19.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Set up a queue using a Foomatic driver
2.Submit a PostScript job
3.Examine the filters used (e.g. cupsctl --debug-logging, then view error_log)

Actual results:
pstotiff is used

Expected results:
pstotiff not used