discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Slight problem w/ fonts


From: Dan Pascu
Subject: Re: Slight problem w/ fonts
Date: Wed, 9 Jan 2002 01:35:46 +0200 (EET)

On  8 Jan, Chris B. Vetter wrote:
> On Tue, 8 Jan 2002 07:43:55 +0200 (EET)
> Dan Pascu <dan@services.iiruc.ro> wrote:
>> On  7 Jan, Chris B. Vetter wrote:
>> > On Tue, 8 Jan 2002 14:43:58 +0530
>> > "V.Krishna Kumar" <birbal77@yahoo.co.in> wrote:
>> > On Tuesday 08 January 2002 08:48, you wrote:
>> >> > I suppose we should really test if adding TrueType fonts by
>> >> > themselves causes the X server to crash or it is mutiple things that
>> >> > cause it to crash.
>> > I haven't been able to crash X through any GNUstep app/tool - yet ;-)
>> No, the X server doesn't crash, but font_cacher does. and this results
> 
> Right.
> 
>> in no font cache being built, and font_cacher is called upon whenever
>> you start a GNUstep app (unless you temporarily disable TT fonts, build
>> the cache then re-enable them).
> 
> Nope. I thought that as well. If I remove Fonts/Cache completely
> and start an app, font_cacher will eventually crash - but there IS
> a new Fonts/Cache/<display> ... the next application will not try
> to re-create a font cache.
> 

I was speaking of the case immediately after I installed gnustep, not
after I used it for a while. right after I installed gnustep, I started
gorm a couple of times and it always launched font_cacher, until I
started font_cacher by hand to see what happens and found out that it
core dumped. then I removed the tt fonts patch from the x server,
started font_cacher by hand, put back the tt font path, and since then
it worked. but if I launch font_cacher now with tt fonts in my path it
core dumps every time. but I guess gorm (and other apps) no longer start
font_cacher because they see there is already a font cache (even if not
up to date).

-- 
Dan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]