Re: Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
On 09/12/2011 06:36 PM, Whit Hansell wrote:
I'm using Wheezy too and had the same problem w. getting a black page in
the browser but it printing ok elsewhere. Now, after today's upgrade, I
no longer get a black page. I get nothing. It won't print. I send the
job and wait and nothing. I have to clear the print jobs but I have to
disable and then enable the printer again to do that. I can however,
print a printer friendly page in the browser. And I can print graphics
when I right clik on the pic and do a view image, then it opens w. only
the picture and that prints fine.
Yes, I'm used to breakage, and don't generally mind it. But this one is
such an unusual case. I usually see all of these testing systems react
in the same manner when an upgrade breaks something. But this time the
older installations are fine while the new ones are affected.
It used to be that every CUPS upgrade would break this particular
printer on every system, and all I had to do was to remove the printer
and re-install it with the hp-setup script.
there is a glitch somewhere in Cups or foo or something. They will get
it figured out but it might take a few more days. That's the "fun" of
Wheezy(testing). Stuff is upgraded and gets broken but in a short period
of time they find the problem and fix it. That's why they tell us not to
use Wheezy for production, but to stay w. stable. I've used testing
since sarge mostly and have gotten used to the intermittent broken
parts. I just found out that Cheese is fixed now again. It's always one
thing or another but we are on the "bleeding" edge as they say. Just
wait a few days. It'll get fixed.
Regards,
Whit
I'm just hoping that the "something" in CUPS or FOOMATIC that is causing
this is actually going to get fixed. If it's a change they needed to
make for an important reason, and if it only broke a few oddball
printers, then the driver for this printer might have to be re-written.
And, IME, that usually takes a while and sometimes doesn't get done at
all if there isn't enough demand for it.
And I love using testing for production -- but only for me and a few
others who are willing to use a work-around or two when something goes
south.
Thank you, Whit, for confirming that I'm not alone with this problem.
Have a good one!
Reply to: