The process "foomatic-rip" stopped unexpectedlywith status 1

[Anonymous]

I have set the LogLevel in cupsd.conf to debug and tried with debug2.
I still get the "Hint: Try setting the LogLevel to "debug" to find out more"
Strange!!!!

This is what I se in the eeror log:
I [09/Dec/2005:15:47:37 +0100] Started "/usr/libexec/cups/cgi-bin/printers.cgi" (pid=248)
I [09/Dec/2005:15:47:40 +0100] Started "/usr/libexec/cups/cgi-bin/printers.cgi" (pid=249)
I [09/Dec/2005:15:47:40 +0100] Adding start banner page "none" to job 384.
I [09/Dec/2005:15:47:40 +0100] Adding end banner page "none" to job 384.
I [09/Dec/2005:15:47:40 +0100] Job 384 queued on 'magicolor_2300W' by ''.
I [09/Dec/2005:15:47:40 +0100] Started filter /usr/libexec/cups/filter/pstops (PID 250) for job 384.
I [09/Dec/2005:15:47:40 +0100] Started filter /usr/libexec/cups/filter/foomatic-rip (PID 251) for job 384.
I [09/Dec/2005:15:47:40 +0100] Started backend /usr/libexec/cups/backend/usb (PID 252) for job 384.
E [09/Dec/2005:15:47:41 +0100] PID 251 stopped with status 1!
I [09/Dec/2005:15:47:41 +0100] Hint: Try setting the LogLevel to "debug" to find out more.

regards


> This is mostly caused by a failure of GhostScript (foomatic-rip is a
> wrapper around GhostScript).
>
> Set "LogLevel" to "debug" in cupsd.conf, restart CUPS, send the job
> again, and post the job-related lines of the error_log file here.
>
> I have CCed Tyler Blessing here, the Foomatic maintainer for Mac OS X.
>
>    Till