I now have done a fix on the GIT of cups-filters (both branches, master
and 1.x) to prevent the error you mentioned.
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 manua
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.
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 mes
[ Re-posting for Daniel Haid, original poster ]
On 18/09/2021 22:30, Daniel Haid wrote:
The entry is not in the 'lpstat -t' output. You are not using the
Brother drivers too, are you? I'm without a good idea here.
No, but I have read that the GTK printing dialog does its own searching
for IPP
On Sat 18 Sep 2021 at 23:55:19 +0200, Till Kamppeter wrote:
[...]
> Due to this technique filter chains can vary between a
> cups-browsed-generated queue and a manually created queue. We will need your
> error_log (in debug mode) to find out what is wrong with cups-browsed's
> filter chain.
Use
On 18/09/2021 22:30, Daniel Haid wrote:
The entry is not in the 'lpstat -t' output. You are not using the
Brother drivers too, are you? I'm without a good idea here.
No, but I have read that the GTK printing dialog does its own searching
for IPP everywhere printers and moreover only sends PDF
The entry is not in the 'lpstat -t' output. You are not using the
Brother drivers too, are you? I'm without a good idea here.
No, but I have read that the GTK printing dialog does its own searching
for IPP everywhere printers and moreover only sends PDF to the printer.
Maybe the problem is tha
On Sat 18 Sep 2021 at 18:42:25 +0200, Daniel Haid wrote:
> > Connected by USB or network?
>
> by network.
>
> > This implies to me that the job is actually printed. Paper comes out of
> > the printer?
>
> Yes, and it comes out correctly. Even two-sided printing works.
That's something, at leas
Connected by USB or network?
by network.
This implies to me that the job is actually printed. Paper comes out of
the printer?
Yes, and it comes out correctly. Even two-sided printing works.
Pleasre give the outputs from 'lpstat -t' and 'driverless'.
Now directly after booting my laptop a
On Sat 18 Sep 2021 at 14:53:31 +0200, Daniel Haid wrote:
> Hello,
>
> I have just installed bullseye and the cups package with all recommended
> dependencies. My printer is a "Brother DCP-L2550DN" connected via lan and it
> works as driverless and is detected automatically.
Connected by USB or n
Hello,
I have just installed bullseye and the cups package with all recommended
dependencies. My printer is a "Brother DCP-L2550DN" connected via lan
and it works as driverless and is detected automatically.
However, although everything seems to work fine, I always get a "printer
error" mess
11 matches
Mail list logo