[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Print file was not accepted (client-error-bad-request)!"



Jeff Licquia wrote:
> On Mon, 2002-11-18 at 18:36, oli wrote:

>> getting "Print file was not accepted (client-error-bad-request)!". after
>> setting loglevel to debug in cupsd.conf, error_log reports :
>> 
>> [19/Nov/2002:00:31:30 +0100] [Job 1] GNU Ghostscript 7.05 (2002-04-22)
>> D [19/Nov/2002:00:31:30 +0100] [Job 1] **** Unable to open the initial
>> device, quitting.
>> D [19/Nov/2002:00:31:30 +0100] [Job 1] Couldn't exec foomatic-gswrapper
>> -q -dBATCH -dSAFER -dNOPAUSE -sOutputFile=- - at /u
>> sr/lib/cups/filter/cupsomatic line 1097.
>
> There's your problem.  You've set up your printer with foomatic, and
> when foomatic does its part to print, gs freaks because it can't open an
> X session.
>
> If gs can't handle being run without an X display, then I suspect all
> manner of things will break.  It's possible, though, that this is a
> problem with foomatic calling gs incorrectly.  Nevertheless, as gs is
> the part that's complaining, I'll assign to gs for further
> investigation.
>
> As a workaround, install cupsys-driver-gimpprint and see if your printer
> is supported in that package.  If it is, try using it; you'll most
> likely be happier with the output anyway.

Well, rats.  Is this still reproducible?  If so, I assume many people
would be very happy to have a testcase that involves a direct gs invocation;
would that be possible to provide?

Thanks for reporting,
Jonathan


Reply to: