Re: Printing works but still getting error messages
On Sun 19 Sep 2021 at 15:28:06 +0200, Till Kamppeter wrote:
> Thanks for the error_log.
>
> The error message
>
> ----------
> E [19/Sep/2021:12:16:51 +0200] [Job 13] File \'\' not found
> ----------
>
> is harmless. It only means that no color management profile is present for
> this printer. In this case a standard profile of Poppler is used.
>
> We should demote this message to DEBUG instead of ERROR level. See
>
> ----------
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Color Manager: Calibration Mode/Off
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Calling
> FindDeviceById(cups-Brother_DCP_
> L2550DN_series)
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Found device
> /org/freedesktop/ColorManag
> er/devices/cups_Brother_DCP_L2550DN_series
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Calling
> org.freedesktop.ColorManager.Dev
> ice.Get(ProfilingInhibitors)
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Calling
> FindDeviceById(cups-Brother_DCP_
> L2550DN_series)
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Found device
> /org/freedesktop/ColorManager/devices/cups_Brother_DCP_L2550DN_series
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Calling
> GetProfileForQualifiers(Gray.Stationery.1200dpi...)
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Found profile
> /org/freedesktop/ColorManager/profiles/Brother_DCP_L2550DN_series_Gray__
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Calling
> org.freedesktop.ColorManager.Profile.Get(Filename)
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Use profile filename: \'\'
> D [19/Sep/2021:12:16:51 +0200] [Job 13] Color Manager: ICC Profile:
> E [19/Sep/2021:12:16:51 +0200] [Job 13] File \'\' not found
> ----------
>
> Otherwise the log makes an impression of a job which has been processed and
> printed correctly. I do not find anything wrong with that.
>
> So all what I can do is demoting the error message to a debug message in the
> cups-filters code, so that print dialogs do not shout it out.
>
> Till
>
> On 19/09/2021 15:07, Daniel Haid wrote:
> > Till, it is exactly as you said: After manually adding the queue, the
> > one from cups-browsed disappeared. Then I removed the manual queue, and
> > the one from cups-browsed appeared again.
> >
> > I enabled debug messages, restarted cups with an empty error_log, and
> > printed once with the queue from cups-browsed (where the error does
> > appear). Unfortunately /var/log/cups/error_log is still 69525 lines
> > long. The error occurs in line 67663. Find attached.
Daniel, do not worry about the error_log size. As you see, the unedited
one enabled the error to be seen in context and an explanation given.
If you are happy with the outcome, we can leave it there, but, before we
finish, I am going to impose on you.
For my records I would like the outpus of
avahi-browse -rt _ipp._tcp
avahi-browse -rt _uscan._tcp
avahi-browse is in the avahi-utils package.
I reckon that the "pdl=" key in the first output will indicate a non-pdf
device.
TIA,
Brian.
Reply to: