cups druckt nicht
Hallo. Ich habe hier einen Rechner mit installiertem
(aktuellen) testing. Wenn ich einen Druckjob abschicke, ist
dieser Job kurz gelistet; dann verschwindet er und steht in
der Liste der abgeschlossenen Jobs als "aborted". Ein Blick
in /var/log/cups/error_log (das Log-level habe ich auf
"debug" gesetzt) zeigt dann dieses:
,----
| D [19/Sep/2003:19:45:52 +0200] [Job 260] foomatic-gswrapper: gs '-dPARANOIDSAFER' '-dNOPAUSE' '-dBATCH' '-sDEVICE=stp' '-sModel=escp2-680' '-sOutputFile=| cat >&3' '/dev/fd/0' 3>&1 1>&2
| D [19/Sep/2003:19:45:53 +0200] [Job 260] AFPL Ghostscript 7.04 (2002-01-31)
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Copyright (C) 2001 artofcode LLC, Benicia, CA. All rights reserved.
| D [19/Sep/2003:19:45:53 +0200] [Job 260] This software comes with NO WARRANTY: see the file PUBLIC for details.
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Unknown device: stp
| D [19/Sep/2003:19:45:53 +0200] [Job 260] renderer return value: 1
| D [19/Sep/2003:19:45:53 +0200] [Job 260] renderer received signal: 1
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Process dieing with "Possible error on renderer command line or PostScript error. Check options.", exit stat: 3
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Possible error on renderer command line or PostScript error. Check options.
| D [19/Sep/2003:19:45:53 +0200] [Job 260] tail process done writing data to STDOUT
| D [19/Sep/2003:19:45:53 +0200] [Job 260] KID4 finished
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Flushing FIFO.
| D [19/Sep/2003:19:45:53 +0200] [Job 260]
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Closing renderer
| D [19/Sep/2003:19:45:53 +0200] [Job 260] KID3 exited with status 3
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Renderer exit stat: 3
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Renderer process finished
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Process dieing with "Error closing renderer", exit stat: 3
| D [19/Sep/2003:19:45:53 +0200] [Job 260] Error closing renderer
| E [19/Sep/2003:19:45:54 +0200] PID 3150 stopped with status 3!
`----
Was will das sagen und was kann man dagegen machen? Kann man
was dagegen machen oder ist das eben -- "testing"?
Holger
Reply to: