Bug#883554: cups keeps breaking network printer with implicitclass:
On Tue, Dec 12, 2017 at 12:10:22PM +0000, Brian Potkin wrote:
> On Wed 06 Dec 2017 at 18:56:33 +0000, Brian Potkin wrote:
> > On Tue 05 Dec 2017 at 19:43:54 -0600, David Fries wrote:
> > > On Tue, Dec 05, 2017 at 01:52:53PM +0000, Brian Potkin wrote:
> > > > On Mon 04 Dec 2017 at 23:47:04 -0600, David Fries wrote:
> > Forget about this. It doesn't help towards a solution and, if I had
> > thought on about it, I should not have sought out the information I
> > was after with that command.
> >
> > What I wanted to find out was whether you used a PPD with the CUPS
> > web interface and an ipp:// or dnssd:// URI. Because you can print
> > (initially at least) it implies you didn't.
I don't know how to answer your question, this is the sequence I do go
get it to print, then after a period of time it reverts to something
that's broken. Does this select a PPD?
Through the web interface I go to modify printer, Discovered Network
Printers, continue, Make: Canon, Model, "Current Driver - Remote
printer: Canon BJC-2100 - CUPS+Gutenprint v5.2.11", Modify Printer.
Then it lists the connection with dnssd://Canon%20BJC-2100%20%40%20...
> > > The majority seems to be different page sizes, dithering, and such.
> > > The header and cupsFilter might be of interest, so included here.
> > >
> > > --- Canon_BJC-2100.ppd 2017-12-05 09:35:07.689792328 -0600
> >
> > This is the PPD on the client?
> >
> > > +++ Canon_BJC-2100_remote.ppd 2015-11-29 00:33:04.432331311 -0600
> >
> > This is the PPD on the server?
No, both were from the client, the Canon_BJC-2100_remote.ppd was from
2015.
> > > lpstat -t
> > > scheduler is running
> > > system default destination: Canon_BJC-2100
> > > device for Canon_BJC-2100: implicitclass:Canon_BJC-2100
> > > Canon_BJC-2100 accepting requests since Tue Dec 5 19:19:12 2017
> > > printer Canon_BJC-2100 is idle. enabled since Tue Dec 5 19:19:12 2017
> > >
> > > How about this sequence, I go through the web interface, change it to
> > > the ipps URI that works. Verify in the browser it is the ipps URI,
> > > verify with `lpstat -t` it is ipps URI, wait until
> > > /etc/cups/printers.conf has the ipps DeviceURI, then.
> > > systemctl stop cups-browsed.service
> > > systemctl start cups-browsed.service
> > > and the browser immediately lists implicitclass:Canon_BJC-2100
> >
> > I can now reproduce your observations, apart from the non-printing
> > aspect.
Do you get implicitclass:Canon_BJC-2100 ?
> > 1. Start with cups-browsed running and no queue using ipp:// or
> > dnssd://. Printing takes place for me. For you I suspect it
> > doesn't. The PPD in /etc/cups/ppd is obtained by cups-browsed
> > from the server and modified slightly. The queue is a raw
> > queue and the PPD is only there so that applications know what
> > to display in their dialogs; it does not lead to any filtering
> > on the client to alter the submitted job file.
> >
> > 2. Configure a raw queue with ipp:// having the same queue name as
> > on the server. This setup method removes the existing PPD and
> > overrides the cups-browsed automatic setup. Printing takes place
> > for both of us.
> >
> > 3. At some future time cups-browsed refreshes what it knows about
> > remote queues, using what is in /var/cache/cups, and reinstates
> > the queue, once again getting the PPD it had in 1. I can still
> > print. (With a different queue name from the server's in 2 you
> > would also be able to print).
> >
> > > I tried printing some text with lpr, after while the state was
> > > aborted.
> > >
> > > lpstat -t
> > > scheduler is running
> > > system default destination: Canon_BJC-2100
> > > device for Canon_BJC-2100: implicitclass:Canon_BJC-2100
> > > Canon_BJC-2100 accepting requests since Tue Dec 5 19:32:48 2017
> > > printer Canon_BJC-2100 is idle. enabled since Tue Dec 5 19:32:48
> > > 2017
> >
> > I would question whether having two queues and two setup mehods
> > managing them is for the best. I'm not saying you shouldn't be able
> > to do it but my advice would be
> >
> > 1. Keep cups-browsed on the client. It automatically sets up print
> > queues from the server's DNS-SD broadcasts. Do not manually set
> > up any other queue.
I'm not sure what I need to do for this. Delete all printers on the
client and something is just magically supposed to work? I go to
manage printers and only one is listed, from what you wrote I expect
you are thinking there are two?
> > 2. Stop (or purge) cups-browsed and set up a queue with an ipp://
> > URI and no PPD (raw).
when you say stop you mean uninstall? This sounds preferable to me, I
give it a ipps URI and it doesn't change it.
> > Both methods have been tested here to work for your printer in your
> > circumstances.
> >
> > Have a look at the server and let us know how you go on.
>
> Any progress on this, David?
Sorry finding time is hard, thanks for being responsive.
--
David Fries <david@fries.net>
Reply to: