search

apple / cups

Apple CUPS Sources
https://www.cups.org
Apache License 2.0
1.93k stars 464 forks source link

Abiword, gedit cause cups to stop the printer with ghostscript 8.15 #1465

Closed michaelrsweet closed 18 years ago

michaelrsweet commented 18 years ago

Version: 8.15.1 CUPS.org User: msg43

If I try to print using abiword or gedit cups will stop the printer. I can print using firefox or vim. This only happens with ghostscript 8.15. I have the latest version of cups and foomatic. I'm using the bjc-7004 foomatic driver but I don't think this really foomatic related unless if there was a major change in ghostscript in which foomatic need to be fixed. Please try to atleast give me a suggestions cause I have not a clue how to fix this.

michaelrsweet commented 18 years ago

CUPS.org User: till.kamppeter

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

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 "). 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.

michaelrsweet commented 18 years ago

CUPS.org User: mike

General support is not available via the STR form. Please post to the CUPS forums and/or mailing lists for general support.

I understand your frustration, however we CANNOT help you via the STR pages; please post your issue to cups.general.