CUPS Update - still can't print

[crispus]

Ok, so I saw the CUPS update today and thought my problems would be solved but alas...

 

updated to CUPS 1.1.21-0.rc1.7.3.101mdk

 

but still cannot print from thunderbird, firefox or OpenOffice. Can print the exact same webpage (google) from Opera. Can print text files and graphics from editors/command line and gimp, respectively.

 

Saw another post about lpr symlink. In a round about way my lpr command points to lpr-cups. Seems ok to me.

 

From my cups error_log:

 

D [18/Jan/2005:17:31:28 -0500] [Job 3] Last OS error: 2

D [18/Jan/2005:17:31:28 -0500] [Job 3] ESP Ghostscript 7.07.2: Unrecoverable error, exit code 1

D [18/Jan/2005:17:31:28 -0500] [Job 3] renderer return value: 1

D [18/Jan/2005:17:31:28 -0500] [Job 3] renderer received signal: 1

D [18/Jan/2005:17:31:28 -0500] [Job 3] tail process done writing data to STDOUT

D [18/Jan/2005:17:31:28 -0500] [Job 3] KID4 finished

D [18/Jan/2005:17:31:28 -0500] [Job 3] Process dying with "Possible error on renderer command line or PostScript error. Check options.", exit stat: 3

D [18/Jan/2005:17:31:28 -0500] [Job 3] Possible error on renderer command line or PostScript error. Check options.

 

Command used by firefox and thunderbird is: lpr ${MOZ_PRINTER_NAME:+'-P'}${MOZ_PRINTER_NAME}

 

but even if I truncate it to lpr it still wont' print.

 

I have no idea how to go about resolving this. Bugging me for awhile now.

 

Anyone have any ideas?

 

-Crispus

[crispus]

I've traced the problem to the inclusion of the filter (or whatever

it is) -dPARANOIDSAFER in the print call. For example, if I enter:

 

cat /usr/share/cups/data/testprint.ps | gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs -sDeviceManufacturer="HEWLETT-PACKARD" -sDeviceModel="DESKJET 932" -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dDuplex=false -r300 -sIjsParams=Quality:Quality=0,Quality:ColorMode=2,Quality:MediaType=0,Quality:Pen

Set=2 -dIjsUseOutputFD -sOutputFile=- - > testfile

 

The command fails but if I remove -dPARANOIDSAFER then the command works

and I can send the testfile to the printer. I understand this was added as

a bug fix but I also found doing a google search that some people found

this tag to be too restrictive. It appears to be the source of my grief

(plug to the help I got from www.linuxprinting.org).

 

How do I remove -dPARANOIDSAFER from my print call?

 

-Crispus

Edited January 24, 2005 by crispus