On Wed, Jun 22, 2022, at 4:32 AM, Patrick O'Callaghan wrote:
(See ... for context)
I have a Brother All-in-one wireless laser printer/scanner which has
worked for years using the manufacturer's driver blob. I now want to
configure it using the printer-driver-brlaser package from the Fedora
repo.
I've uninstalled the original Brother driver and deleted the printer
config using the CUPS interface.
I then added a new printer using the KDE System Settings widget, and
attempted to print a test page. This appears to go through, but then
the queue status shows "Unable to locate printer".
I deleted that configuration and tried again using the CUPS web
interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
Printing a test page again shows "Unable to locate printer". This
happens both using the generic IPP driver and the specific model driver
from the RPM package.
The CUPS systemd service and AVAHI daemon are both running, as is
systemd-resolved, which handles DNS-SD (I reloaded the latter just in
case.)
I'm out of ideas. To repeat: both printing and scanning work correctly
with the manufacturer's driver, so it's not a hardware or connection
problem.
Any thoughts before I give up and revert to the binary blob?
George might have the final answer, maybe your model will only work via a USP connection
if using the brlaser option.
But, I checked my virtual machine to see how it is connecting to the printer...
Brother_DCP-L2550DW_series
Brother_DCP-L2550DW_series (Idle, Accepting Jobs, Not Shared)
Description: Brother DCP-L2550DW series
Location:
Driver: Brother DCP-L2550DW series, using brlaser v6 (grayscale, 2-sided printing)
Connection: dnssd://Brother%20DCP-L2550DW%20series._pdl-datastream._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4d12445
Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=two-sided-long-edge
So it does seem to be using dnssd. This is a pretty generic F36 XFCE install so I did not
do much to get that working, mostly just needed to start cups.