On Wed, Jun 22, 2022 at 8:32 AM Patrick O'Callaghan <pocallag...@gmail.com> 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/ > I suspect this detection doesn't adequately check the details of the IPP support. Given the age of the printer, IPP may not be implemented "properly" by current standards. > 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. > I looked at the Brother DCP-7055W Advanced User's Guide, which is dated 2012. I can't see any mention of IPP or AirPrint. https://discussions.apple.com/thread/7199902 says this model was not on Apple's list of supported printers for AirPort in 2015. https://wiki.gentoo.org/wiki/Brother_networked_printer says the printer works, but gives no configuration details https://www.pwg.org/ipp/ippguide.html tells you to "Consult your Printer documentation or the Printer's Bonjour (DNS-SD) registration information to determine the proper hostname, port number, and path to use for your Printer." It would be interesting to know why IPP is failing, but I suspect you are stuck with Brother's rpm. > 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? > > poc > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- George N. White III
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
