i gave a very similar problem to codex and it saw that in about 10 minutes. i just told it about the problem and it changed whatever on the system to make the damn thing work.
On Mon, Mar 16, 2026 at 9:42 PM David Wright <[email protected]> wrote: > On Sat 14 Mar 2026 at 12:10:49 (-0400), songbird wrote: > > Paul Scott wrote: > > > On 3/12/26 12:23 PM, Charles Curley wrote: > > >> On Thu, 12 Mar 2026 10:25:39 -0700 > > >> Paul Scott <[email protected]> wrote: > > >> > > >>> W [12/Mar/2026:00:57:05 -0700] Printer drivers are deprecated and > > >>> will stop working in a future version of CUPS. See > > >>> https://github.com/OpenPrinting/cups/issues/103 > > >>> > > >>> I went to the link but I don't know enough to know what it means and > > >>> more importantly how I can fix printing. > > >> When we deprecate a feature or capability in CUPS, we are > > >> announcing the intention to stop supporting it in the next major > > >> release of CUPS, in this case CUPS 3.0. Given the historical pace > > >> of CUPS development, that usually means you have years to make > the > > >> transition. In the case of printer drivers, we made the conscious > > >> choice to have Printer Applications in place before releasing > CUPS > > >> 3.0. And since Linux distributions typically lag behind the > > >> “bleeding edge” of CUPS development, you can expect to be able to > > >> use printer drivers for few more years after CUPS 3.0 is > released. > > >> > > >> https://openprinting.github.io/cups/drivers.html > > >> > > >> The current version of CUPS in trixie is 2.4.10-3+deb13u2. In > > >> forky/sid, 2.4.16-1 (subject to change). So this likely won't affect > > >> you for the foreseeable future. > > > > > > Running sid. I upgraded hplip to 3.22.10+dfsg0-? when I saw the > problem. > > > > > > I do have cups 2.4.16-1 > > >> > > >> Furthermore, the intent appears to be to replace drivers in CUPS with > > >> what they call printer applications. The existing printer applications > > >> are based on the CUPS drivers they are replacing. So unless you have a > > >> really oddball printer you are probably safe going to CUPS 3.0. > > >> > > >> https://openprinting.github.io/cups/drivers.html > > > > > > I don't understand enough of that to diagnose my problem. > > >> > > >> Since I have no idea what your current problem is, I can't help you > > >> with it. But I don't think the deprecation of drivers is related to > > >> your problem. > > > > same here, i happened to be in the middle of taxes and > > such when i did the cups update (via Debian testing) and > > it stopped working. oops. luckily i did have an existing > > stable partition which i was able to use for printing > > what i was in the middle of doing. > > So summing up we have the following: > > A message /warns/ that in several years time new versions of Cups > won't work with the current generation of printer drivers. > > Two openprinting links explain how and why Cups will make that > transition. > > The OP runs cups 2.4.16-1, released back in December 2025. > > The OP upgraded hplip to 3.22.10+dfsg0-? (presumably > 3.22.10+dfsg0-8.1), released back in April 2025. > > The OP can't print on an HP P1006 from a certain machine. > We're not told which. > > The laptop can't print wirelessly to the printer, which doesn't > appear to be a wireless printer anyway. > > Printing worked a few days ago. It's implied from linux, but > but not by which machine and through what connection. > > A machine running Windows, presumably connected by USB, can print. > > It's not clear what's implied by "same machine". Does it refer back to > the laptop? Or does it refer back to whatever was working a few days > ago? Or does it refer forwards to the machine that's connected to the > printer (ie "same" is redundant)? > > Or perhaps it's this scenario: the laptop should be able to print > wirelessly via a router to a server connected to the (shared) printer, > the server machine being able to run either Windows or linux. > (Else why did the laptop try to print wirelessly?) > > "Can't print" is the only actual symptom that I see described here, > so perhaps it doesn't really matter what refers to what. > > Yes, perhaps AI can see its way through all that. > > Cheers, > David. > >
