Re: Freetype and Seamonkey

Dave Parsons wrote:
> On 01-06-19 04:29, Dave Yeo wrote:
>> Dave Parsons wrote:
>>> 0012DE40 : 524F4241 75203A54 6C62616E 6F742065 : ABORT: unable to
>>>  0012DE50 : 6E696620 20612064 62617375 6620656C :  find a usable f
>>>  0012DE60 : 20746E6F 72657328 3A296669 6C696620 : ont (serif): fil
>>>  0012DE70 : 3A442065 6573552F 642F7372 2F6B696D : e D:/Users/dmik/
>>>  0012DE80 : 626D7072 646C6975 4955422F 6D2F444C : rpmbuild/BUILD/m
>>>  0012DE90 : 6C697A6F 6F2D616C 462D3273 46455249 : ozilla-os2-FIREF
>>>  0012DEA0 : 345F584F 5F395F35 72736530 4C45525F : OX_45_9_0esr_REL
>>>  0012DEB0 : 45534145 32534F5F 3241475F 7866672F : EASE_OS2_GA2/gfx
>>>  0012DEC0 : 6568742F 2F736562 54786667 52747865 : /thebes/gfxTextR
>>>  0012DED0 : 632E6E75 202C7070 656E696C 36383120 : un.cpp, line 186
>>
>> This seems to be the problem.
>> What happens if you run (without quotes)
>> "fc-match serif"
>
> E:\>fc-match serif
> DEJAVUSERIF.TTF: "DejaVu Serif" "Book"

Weird, it should use that. I guess it could be profile related. Have you 
tried a fresh profile? if that works, you could backup prefs.js and then 
search for serif and try removing any lines that reference it.
Really I guess a bug report should be filed against fontconfig as this 
is a definite regression and even if there was no matching serif, it 
should fall back to something. fc-match -s serif should give a list of 
fallbacks.

>
>
> Unfortunately SET LIBCX_HIGHMEM=2 didn't help with AOO.
>

Too bad, thought I saw someone used that as a solution. Have you tried 
running it on a freshly booted system?
Dave