On Fri, Mar 06, 2026 at 12:40:30PM +0100, Antony Stone wrote:
> On Friday 06 March 2026 at 12:33:45, Haines Brown via Dng wrote:
>
> > On Thu, Mar 05, 2026 at 07:06:41PM -0700, Gregory Nowak via Dng wrote:
> > > On Thu, Mar 05, 2026 at 06:44:51AM -0500, Haines Brown via Dng wrote:
> > >
> > > > How would I know if a bug has been reported? A quick search
> > > > returned nothing.
> > >
> > > reportbug cups-browsed
> >
> > Thanks, Greg. Helped.
> >
> > It is a known bug. Downgrading from excalibur to dedalus seems best
>
> Can you use your Daedalus machine to get the printer configuration file for CUPS
> and then simply copy that to the Excalibur machine, as though you had created
> it manually?

Good thought, Antony, but didn't work.

This is a known bug in cups-browsed Version: 1.28.7-1. The
version installed for Excalibur is Version: 1.28.17-6+deb13u1

A work around for the 1.28,7 version is:

# apt install apparmor-utils
# aa-complain cupsd-browsed
# systemctl restart cups-browsed

What does that second line, aa-complain, refer to? Something to do
witn apparmor?

I'm surprised that folks on this list who have upgraded to
Excalibur have not reported problems with printing.

--

Haines Brown