Geoman wrote:
I installed Firefox3 from Nekoware/stable using nekosync on my 'new'
Octane/SSI
(fresh install of 6.5.16 then patch 5086 then update to 6.5.22). On start I get:
Code:
Select all
IRIS 1% firefox3
Fontconfig error: Cannot load default config file
Since I've just been through this ... you've got errors in your fonts setup. You're not seeing them in other programs because the traditional apps use X but Fireflop is dependent on freetype and fontconfig. Fireflop3 definitely needs fontconfig running correctly to work.
Even in a generally usable state, I was seeing the occasional pango gdk-pixbuf etc warning: notices, followed shortly by a crash. With my current well-oiled highly-tuned font setup, those have gone away completely.
(Still get the occasional std:badalloc and a core dump tho. Not too often but once in a while.)
Firefox2, on which I'm typing this, is running flawlessly.
And displaying in a 4" wide stripe down the center of the window
Unfortunately, Flop2 doesn't work correctly on a whole bunch of sites.
You're right, it did not seem to be as persnickety, tho.
You may have some other problems too, but the errors you are getting are exactly the same as what I was seeing, which are now corrected by fixing the fonts setup. And I finally got the chinese working, too. Yay !
A word of warning : if you only mess around with fontconfig, you're safe. I think canavan put a working nekoware setup in fonts.conf (or whatever the config file is named). Make your additions to a file < local.conf > and save backups.
But if you dive deeper and make changes to X,
definitely
save the originals so that when you single-user in, all you have to do is some renaming. If your fonts setup is screwed up, it's quite possible that you won't be able to start X. This is an uncomfortable situation
(And kind of a stupidity on X'es part, if you ask me. But nobody did, so it is what it is ...)
Also if you make changes to the X end of things, do
not
repeat do
not
forget as root to < xset fp rehash > after you make any changes or you will be sooo sorry.
You can also set the bootup screen to verbose, that will give you some hints - such as "Error in item 3 of fontpath, starting from 0" right before XSgi refuses to start.
It was worth it in the end tho, imo. Now when I ask for Helvetica, I
get
Helvetica. The very same Helvetica that the printer uses, not something kinda-sorta similar.