CUPS sucks!

[Helge Blischke]

ncoesel wrote:

>> ncoesel wrote:
>>
>> >> On Aug 21, 2009, at 12:23 AM, ncoesel wrote:
>> >> > I've spend the last two days trying to get cups to work on an
>> >> > embedded platform.
>> >>
>> >> Um, CUPS is currently not supported on any embedded platforms,
>> >> although I do know of several people playing with it there.
>> >
>> > Huh??? Linux is linux. No matter what the platform is! You're probably
>> > referring to Linux distributions. The difference between distributions
>> > (paths & users) is usually covered by the automake/autoconf settings.
>> >
>> >> > The major problem I'm experiencing is that Cups provides no
>> >> > diagnostic information at all so I don't know what I must fix.
>> >>
>> >> You mean cupsd was not generating an error_log file listing the errors
>> >> it found?
>> >
>> > I've set the level to debug2. But it is not generating meaningfull
>> > errors. I'd expect if it finds a USB device port but can't access it,
>> > it reports an error in the log. The software I write does stuff like
>> > that and also provides hints to fix problems.
>>
>> Perhaps you could supply a sample error_log to look into in order to deal
>> with your complaints?
> 
> The error when trying to print a test page:
> 
> D [01/Jan/1970:03:23:22 +0000] Print-Job
> ipp://localhost:631/printers/Labelwriter D [01/Jan/1970:03:23:22 +0000]
> Print-Job client-error-document-format-not-supported: Unsupported format
> 'application/postscript'! D [01/Jan/1970:03:23:22 +0000]
> cupsdProcessIPPRequest: 9 status_code=40a
> (client-error-document-format-not-supported)

You need to supply
(1) the complete log dealing with the print job (the test page in this case)
(2) the printer's device uri
(3) the printer's PPD
(4) the xxx.types and xxx.convs files from your /etc/cups (or whatever cups 
resides) directory.

I've - among other things - installed and administrated cups systems for 
more tha n half a decade on various systems (Linux, UnixWare, SunOS 4,
Solaris (from 2.5 to 10), Mac OS X) and never needed more that roughly
an hour to find out the cause for errors like you describe.

Helge