openoffice.org fonts vs. galeon / mozilla
After performing the fix that Chris Halls gave me, openoffice starts up
fine.
However, I am not able to start up galeon or mozilla. The reason I
think that this is worthy of posting to this list is as follows:
When I 'strace mozilla', one of the last things that it does positively
(as opposed to unlinking a temp file) is to open up an openoffice.org
font file. I found this a bit odd, so I did 'strace galeon', and got
another segfault, pointing to the same font file. I moved that font
file to a backup directory (mv
/usr/share/fonts/truetype/openoffice/timmonsr.ttf
/usr/share/fonts/truetype/openoffice/backup/ ) and did the two commands
again. mozilla errored again, on a different font.
Interestingly enough, just running 'galeon', without strace, gave me
this error.
font /usr/share/fonts/truetype/openoffice/timmonsr.ttf 0 glyphs
and the "0 glyphs" message squirts out every time either mozilla or
galeon die. After all "0 glyphs" fonts are nuked out of the way, galeon
and mozilla both start up and run fine.
Also, even though my /usr/share/fonts/truetype/openoffice
directory has only these
fonts.scale helmetcr.ttf starmath.ttf
fonts.dir helmetcb.ttf starbats.ttf
files in it (and I didn't update the fonts.scale or the fonts.dir) files
at all after moving files around) and my backup directory has
ariosob.ttf congab.ttf helmetcbi.ttf timmonsb.ttf
ariosor.ttf congar.ttf helmetci.ttf timmonsbi.ttf
chevaraor.ttf helmetb.ttf helmeti.ttf timmonsi.ttf
chevarar.ttf helmetbi.ttf helmetr.ttf timmonsr.ttf
in it, staroffice starts up and works fine.
Is this a bug with the ms-ttcorefonts package?
rob
Reply to: