Re: Freetype and Seamonkey

Dave Parsons wrote:
> On 08-06-19 10:02, Dave Parsons wrote:
>> On 07-06-19 03:54, Dave Yeo wrote:
>>> Dave Parsons wrote:
>>>> On 06-06-19 16:52, Dave Yeo wrote:
>>>>> Can you or/and Harald, while using the newest fontconfig and after a
>>>>> reboot, post the output of
>>>>> fc-cache -f --verbose
>>>>> Thanks
>>>>> Dave
>>>>
>>>> I'll do it tomorrow if it is still needed.
>>>> Which do you mean by newest fontconfig? I see nothing new on ANPM.
>>>> From the OS2World thread and the TRAC ticket 210, I get the impression
>>>> that there is a newer version available on the testers list. If so I
>>>> can't access it.
>>>
>>> I meant fontconfig 2.13.1-2 and freetype 2.10.0-1, which I thought that
>>> you had upgraded too.
>>> Dave
>>
>> OK, output from  'fc-cache -f --verbose' attached.
>>
>> As David Graser reported on OS2World, Firefox now works.
>>
>> Dave P.
>>
>
> Following up on a comment by diver about mozturbo I just tried without
> any *Turbo running.
> No difference as confirmed by a diff of the output from fc-cache,
> firefox started & ran successfully as wanted.

Good to hear that it is now working for you. Just leaves Harald to 
figure out and still the question while you and David had so many problems.
As for mozturbo, it will keep DLLs locked and when upgrading any Mozilla 
dependencies, it should be unloaded or the system rebooted, though for 
most upgrades it probably don't matter much. The problem with fontconfig 
is the XML setup files changed this upgrade.
Dave