| |||||||||||||
Another regressionAnother regressionPosted May 27, 2008 13:56 UTC (Tue) by dskoll (subscriber, #1630)In reply to: Another regression by roc Parent article: Fsyncers and curveballs (the Firefox 3 fsync() problem)
I guess GTK's print setup is broken somehow on your system. Very possibly; this is on Debian Etch which is too "ancient" for the Firefox gurus. I had to install a private copy of gtk+ Every time we try to make people happier with deeper GTK integration, AIEE. Every time Firefox gets deeper GTK integration, I get unhappier, because formerly-working stuff starts breaking, or formerly-fast stuff gets miserably slow (ie, the grotesque GTK+ file browser which mercifully can be turned off in about:config) Anyway... even if CUPS is busted, Firefox should at a minimum offer to produce a Postscript file. Printing using "lpr" works fine for me if only I could convince the #*$&&*#$ web browser to write a Postscript file...
(Log in to post comments)
VERY bad idea Posted May 27, 2008 21:33 UTC (Tue) by khim (subscriber, #9252) [Link] Anyway... even if CUPS is busted, Firefox should at a minimum offer to produce a Postscript file. To make it happen you need to keep the whole another printing library around. That's Windows way: sure with Windows NT core it's easy, but Windows95 it's still popular so let's use old library. And then plug new one in old if we need some effects. Then and patches to fix gotchas and another patches to fix problem introduced by patches. Then 10 years down the road you need 2GB or RAM and two cores just to print two pages of text. Not a good idea. May be it was to early to switch to gtk-print, may be not (after all Firefox is not released yet and may be Debian will manage to ship another release before that happens), but to have TWO print subsystems is just crazy.
|
|||||||||||||