I can’t seem to print after this update. Did something change with CUPS?
Tried removing and adding the printer again. Tried printing test pages. Nothing works.
This is on 2 systems, one a laptop and one a desktop.
Just tested from a Windows machine to make sure it is not the printer and the printer prints fine.
Tested pinging the printer now. Responds fine.
Seems like nothing stays in the printer queue and it never reaches the printer.
This suggests that it would be a network printer. Is avahi-daemon running?
systemctl status avahi-daemon
It was not running… I enabled it and it is running now. Still nothing is printing.
systemctl status avahi-daemon ✔
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset>
Active: active (running) since Thu 2025-05-15 12:12:23 PDT; 1min 45s ago
Invocation: f0449e1f3453485aa9bb62bad1c57ce1
TriggeredBy: ● avahi-daemon.socket
Main PID: 793 (avahi-daemon)
Status: "avahi-daemon 0.8 starting up."
Tasks: 2 (limit: 38254)
Memory: 1.1M (peak: 1.7M)
CPU: 15ms
CGroup: /system.slice/avahi-daemon.service
├─793 "avahi-daemon: running [x-x570steellegend.local]"
└─800 "avahi-daemon: chroot helper"
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: New relevant interface lo.IPv>
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: Joining mDNS multicast group >
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: New relevant interface lo.IPv>
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: Network interface enumeration>
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: Registering new address recor>
May 15 12:12:23 x-x570steellegend avahi-daemon[793]: Registering new address recor>
May 15 12:12:24 x-x570steellegend avahi-daemon[793]: Server startup complete. Host>
May 15 12:12:27 x-x570steellegend avahi-daemon[793]: Joining mDNS multicast group >
May 15 12:12:27 x-x570steellegend avahi-daemon[793]: New relevant interface enp7s0>
May 15 12:12:27 x-x570steellegend avahi-daemon[793]: Registering new address
And is cups running? 
systemctl status cups
Yep!
systemctl status cups INT ✘ 3m 14s
● cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabl>
Active: active (running) since Thu 2025-05-15 12:12:24 PDT; 5min ago
Invocation: 0410950e5284467dba2ca9c3f7cc2c17
TriggeredBy: ● cups.socket
● cups.path
Docs: man:cupsd(8)
Main PID: 877 (cupsd)
Status: "Scheduler is running..."
Tasks: 6 (limit: 38254)
Memory: 69M (peak: 278.6M)
CPU: 6.516s
CGroup: /system.slice/system-cups.slice/cups.service
├─ 877 /usr/bin/cupsd -l
├─ 930 /usr/lib/cups/notifier/dbus dbus://
├─ 933 /usr/lib/cups/notifier/dbus dbus://
├─2184 /usr/lib/cups/notifier/dbus dbus://
├─2185 /usr/lib/cups/notifier/dbus dbus://
└─2186 /usr/lib/cups/notifier/dbus dbus://
May 15 12:12:23 x-x570steellegend systemd[1]: Starting CUPS Scheduler...
May 15 12:12:24 x-x570steellegend systemd[1]: Started CUPS Scheduler.
I shut down the firewall to make sure that was not doing anything. No go.
The job appears in the printer queue, and then disappears without printing.
I’ve moved this into its own topic, as it may help. Please feel free to change the title etc. if needed. 
I think I have a solution… Found this in the CUPS logs:
Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103
Well, it may be the cutoff for that. So i tried installing a Driverless driver, and it is printing again.
Thanks for all the help trying to troubleshoot this.
Digging deeper into this, I really don’t want to run Avahi on a laptop connecting to wireless public hotspots and driverless printing seems to require that. This is a massive security risk.
I think what is broken is the jetdirect capability. It is not really a driver issue as the logs would have told me it no longer works.
Any idea of workarounds?
Seems it has happened to Arch recently too:
https://bbs.archlinux.org/viewtopic.php?id=305329
User reports this is the problem:
Got it! :-)
The culprit is **libxml2 (2.14.2-2)**.
Just downgrading it to **libxml2 (2.13.8-1)** (and its two dependencies **libarchive (3.7.9-2 -> 3.7.9-1)** and **sane (1.3.1-3 -> 1.3.1-2)** solves the problem.
New solution for Canon printers at least is the following package:
cnrdrvcups-lb
I am good to go again now without having to use Avahi
Note that this is why I don’t want to use Avahi. This list keeps growing:
Not to mention it advertises everything your system does to all those around you. It is probably fine most days, but if you don’t need it, disable it in my mind.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.