Re: [Splix-devel] First check

[Chuck H. <cfh...@er...>]

Hi Aurelien,

I just took a really careful look at the error_log messages from the
samsung/xerox proprietary filters, and the splix filters.  Someone had
told me that the samsung/xerox filters were using pstoraster, but I see
from the error_log that actually, they aren't.  They have incorporated their own
version of pstoraster in the samsung/xerox proprietary filter.

That explains the big difference in the error_log files between the two
filters.

I really would prefer to leave the debug messages on.  They are very useful
when you are making ppd and filter changes in CUPS.  So, I guess I will go
and find the problem in pstoraster, fix it, and submit a bug report.

-Chuck




Aurélien Croc wrote:
> Le samedi 25 novembre 2006 02:14, vous avez écrit :
>>   This is *not* normal!  This error_log *should* be telling you something.
> 
> The capital D at the left of each line indicates that it is a DEBUG message 
> and *NOT* a warning or error message. Then this message can be useful for 
> pstoraster developers. Not for me!
> 
> If these messages are *not* normal, congratulation, you found a bug in the 
> pstoraster! 
> 
>> But it is doing something else that is very wrong to the cups system.
> 
> I'm just using a specific pstoraster translation which may be not used by the 
> other ones (Since I never saw these lines for my black and white printer, it 
> seems that this is a bug in the pstoraster filter during the postscrip -> 
> CMYB paged translation. (It exists lots of other translations).
> 
> Finally, since these messages are not important (debugging message), just 
> change the LogLevel from debug to error or info in the cupsd.conf and you 
> won't see anything anymore. (Or write a bug report to CUPS or try to find the 
> bug and make a patch (It seems to be a debug message printf located in a 
> loop.. So just put these printf outside the loop and everything will be ok)).
> 
> Regards, 
>