[WORKAROUND] Re: Etch/Cupsys/Gutenprint - failure to communicate
I don't think this made it to the list...
----- Forwarded message from Matthew Krauss -----
> From: Matthew Krauss
> Subject: Re: Etch/Cupsys/Gutenprint - failure to communicate
> Date: Tue, 07 Nov 2006 11:31:31 -0500
> Florian Kulzer wrote:
> >On Fri, Nov 03, 2006 at 12:02:32 -0500, Matthew Krauss wrote:
> >>George Borisov wrote:
> >>>If all else fails, get hold of the PPD file and copy it into the
> >>>"/usr/share/cups/drivers" folder. That should ensure that Cups
> >>>can see it.
> >>Thanks, I tried that, but it still does not show up.
> >What happens if you go to the http://localhost:631 frontend, use "add
> >printer" and point CUPS to the PPD file manually? (at the "or provide a
> >PPD file" text input box with the "browse" button next to it)
> It's like magic. Amazing.
> Thank you.
> For anyone searching the archives, the file used (according to above
> instructions) is the following:
> The freaky thing is I could *swear* that I tried this before. I only
> tried it again so I could give you a proper answer to your question.
> Notably, I find that gnome-cups-manager and other cups front-ends are
> completely confused by this. They don't identify the printer and won't
> work with it correctly; so I am going to have to stick to the web
> interface for a while, I guess. No problem there, I used it for years
> in the past.
> Thanks again,
----- End forwarded message -----