On Tue, 28 Sep 2004 06:20:04 +0200, Marc Wilson wrote: > > On Mon, Sep 27, 2004 at 07:43:52PM -0500, Christopher L. Everett wrote: > > Marc Wilson wrote: > > > Sure. Don't use xprint. Mozilla is perfectly capable of generating > > > printed output on its own. > > > > > Yah, but for some reason when I remove Xprint, Mozilla starts > > groveling: I wait for a bloody eternity before the print dialog comes > > up, and while I wait, Mozilla pretty much freezes. > > Dunno... I installed CUPS on a throwaway box here to see if it was still > as craptastic as it's always been (it's still an overengineered POS), > but it doesn't do THAT. Moz prints right away, just like always. > > Of course, Xprint has never been installed on this box. Perhaps there's > some detrius in one of Moz's labyrinth of config files that's making it > look for it. Have you tried moving your ~/.mozilla directory out of the > way and seeing if that cures the situation?
Double-check that you are starting Mozilla from a shell without the variable $XPSERVERLIST set. I think this is what causes eternity??? (I believe I had to log out and log back in again to make the damned thing go away permanently.) HTH Reid
