Hi! I had this problem myself on the very first system I upgraded from woody to sarge. I tried the "100 character long workaround" that was suggested on the printed error message: it managed to make the error go away, but produced a printed page where every character is displayed as a blank rectangle.
Then I found this bug report, and tried the workaround suggested by Margarita. It worked great! :) All printing difficulties seem to have disappeared suddenly after I commented out that line in /etc/mozilla/prefs.js and restarted my gecko-based browser (Galeon)! Thanks Margarita, you saved my day! ;-) Unfortunately, I later noticed that this workaround has a bad interaction with the libmozsvgdec.so plugin. Actually when I try to display an SVG image with Galeon, I get a dialog with the following error: | The Libart/Freetype SVG rendering engine could not initialize the | freetype library. Please go to | http://www.mozilla.org/projects/fonts/unix/enabling_truetype.html and | follow steps 2-7. and the SVG image is rendered with no texts inside. If I re-enable the line pref("font.FreeType2.enable", true); line in /etc/mozilla/prefs.js, then the error dialog goes away and I can see the SVG image. Well, fonts do not really look right (sodipodi and inkscape display the image differently) and I see no color gradients, but that's probably an issue with the libmozsvgdec.so plugin, so it's off-topic here... -- :-( This Universe is buggy! Where's the Creator's BTS? ;-) ...................................................................... Francesco Poli GnuPG Key ID = DD6DFCF4 Key fingerprint = C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgptIJIZtGpKh.pgp
Description: PGP signature
