[cups.bugs] Re: [HIGH] STR #1465: Abiword, gedit cause cups to stop the printer with ghostscript 8.15

[Till Kamppeter]

[STR New]

At first, use the debug mode of CUPS, as CUPS and foomatic will give you a
lot of information then. To get CUPS into the debug mode, edit
/etc/cups/cupsd.conf, setting the "LogLevel" to "debug" and then
restarting the CUPS daemon (usually "killall -HUP cupsd" or
"/etc/init.d/cups restart").

After that do (as root)

cancel -a
/usr/bin/enable <name of your print queue>

and send another print job. Wait until "lpstat -p" shows the queue as
"disabled" again. Then take a copy of /var/log/cups/error_log and attach
it to this report.

Have a look into the /var/log/cups/error_log file and you will see a lot
of info produced by foomatic-rip (Lines contain "Job <number>"). Search
for the line with "renderer command:" in it. This line shows you the
ghostscript command line. So you can try also to run GhostScript manually
with the same parameters. Do

cat /usr/share/cups/data/testprint.ps | gs ... > gs.out

Paste the GhostScript command line at the place of "gs ...". Remove the
"-q" from the command line to get more error output.

See also error messages of GhostScript after the "renderer command:" line
in your error_log file. Are there error messages? Are they the same when
running GhostScript manually? Post the messages here.

Or is GhostScript working nicely? Then you should check whether the
printer is able to print the job. Do

cat gs.out > /dev/lp0

or

cat gs.out > /dev/usb/lp0

If this works, try also

lpr -o raw gs.out

to test only the CUPS backend.

Link: http://www.cups.org/str.php?L1465
Version: 8.15.1