You are not logged in.
Oh boy. Deprecated 6 years ago! How did I miss that!?
Offline
Good idea, I filed deletion requests for cndrvcups-lb and cndrvcups-common-lb.
Also removed the reference to them from the wiki.
This worked for me. MF8280Cw
Offline
An attempt at a brief summary:
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.
seth wrote:Do you get away w/ https://archlinux.org/packages/extra/x8 … l2-legacy/ ?
Yes, using the "legacy" package works around having to downgrade the libxml2 package (and its two dependencies). Back in (printing) business again without having to downgrade anything (Arch is up to date + libxml2-legacy installed). [...]
themew wrote:Are you seeing any issues when downgrading libxml2?
No issues, but I only used that workaround for about 10 minutes, because I switched to libxml2-legacy package and everything works fine now without having to downgrade anything.
seth wrote:iq2luc notably also downgraded its apparently two only consumers on that box, but that's not gonna be your average desktop system: https://archlinux.org/packages/core/x86_64/libxml2/
Not just two... [...] ...but still, in my opinion your suggestion for installing libxml2-legacy should be the "official" workaround / solution for the time being. [...]
@iq2luc and @seth:
Do I get you right that, if the system had not been rolled back, then all that would have needed to be done to was to install libxml2-legacy, and nothing more?
Please excuse my "stupid" question, but I am struggling to keep track of what you actually did, and narrow it down to the necessary actions. I'm having issues of my own with my Epson printer. I thought I had solved it, but unfortunately my printer did not work for very long. I am trying to figure out if the issue discussed in this thread might also apply to me, in addition to the issue that I had before.
Offline
If this is a binary-only driver that cannot be recompiled by anyoen (but canon's lazy ass) then yes, installing libxml-legacy will most likely solve that problem and a couple of AUR drivers already depend on it.
https://bbs.archlinux.org/viewtopic.php?id=304707 however predates the breaking libxml2 update, https://archlinux.org/packages/extra/x86_64/gutenprint/ is in the repos, doesn't depend on libxml2 and afaiu your thread revolved around some (dated) mystery ppd you had to update?
Online
Had the same issue with my LBP253x and the solution I found here didn't work. In an act of desperation I just changed the model to "Generic PostScript Printer" and... it worked.
Offline
[...]https://archlinux.org/packages/extra/x86_64/gutenprint/ is in the repos, doesn't depend on libxml2 and afaiu your thread revolved around some (dated) mystery ppd you had to update?
I guess you are right. The reason why I looked into this, was that I got lines like the following one in my /var/log/cups file, and wondered if it could be somehow related to what you discussed about IPP and IPPS:
E [02/May/2025:18:14:33 +0200] [Client 46] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/95) from localhost.
But today, as a blindshot, I tried running this:
[foo@bar ~]$ sudo /usr/bin/cups-genppdupdate
[foo@bar ~]$ sudo systemctl restart cups
And lo and behold, my printer is working again... at least for now. After updating Cups to version 2:2.4.12-1, Cups/Gutenprint seems to have become a bit moody towards my printer. Even at this time, despite the printer working, I am still getting warnings like this:
W [19/May/2025:16:21:49 +0200] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103
Offline
That error message is normal and I'm generally not sure how they envision to actually act on that warning as that would make a huge number of printers incompatible "just cause", but yes this of course reduces the maintaining surface considerably...
That you need to upgrade gutenprint drivers is also normal after every update of the gutenprint package, there's a post-upgrade/install message indicating that necessity.
Offline
That error message is normal [...]
Are you referring to the IPP client-error-not-possible message marked with an E, or the deprecated printer drivers message marked with a W? Which one of them should I ignore?
Offline
The W warning. But actually looking at the mentioned bug report, most of the open driver projects like gutenprint will eventually implement an IPP driver mapping their old PPD implementation, so for actively maintained projects the fallout might not be as bad as I feared.
If you're using the gutenprint/PPD drivers anyway you can probably ignore IPP based failures for the time being.
Offline