Re: [Fresco-devel] Berlin starts, fresco-demo fails

On Sun, Apr 06, 2003 at 01:44:53AM +0000, Nicolas Souchu wrote:
> 
> Good news, Berlin starts if I carefully unset BERLIN_FONT_CHOOSER. No Font
> is ask when starting. Is that different from starting with BERLIN_FONT_CHOOSER="" ?

BERLIN_FONT_CHOOSER unset means, "pick a default font".  (I think its
notion of "default" is, "the first one freetype actually manages to
load").  BERLIN_FONT_CHOOSER set to "" means, "give me a list of all
fonts freetype manages to load, and let me pick one".
BERLIN_FONT_CHOOSER set to a number means, pick that number font (it's
the same number as you're prompted with when you set it to "").

> Then logging gives:
> 
> >>>
> [1.5472:0:text] libArt::FTFont: scanning font dir /usr/lib/X11/fonts/Type1
> [1.54918:0:text]        libArt::FTFont: can't open font /usr/lib/X11/fonts/Type1
> /UTBI____.afm
> [1.55585:0:text]        found FT-readable font Utopia (1) Bold Italic (2) in /us
> r/lib/X11/fonts/Type1
> [1.55806:0:text]        libArt::FTFont: can't open font /usr/lib/X11/fonts/Type1
> /UTB_____.afm
> <<<
> 
> Is that harmless or would it explain that later,
> (I'm running fresco-demo)

I think it should be harmless, as long as it finds _some_ font.  Which
apparently it is.

> >>>
> unable to create one of the demo applets
> this probably means that the server doesn't provide
> some of the resources requested by this applet
> <<<
> 
> The server is healthy (pointer ok) and the tracing output is very productive,
> but I get nothing more than a black screen.

I'd check the kit loading to see if the kits were all being loaded all
right?  And look at the trace output for when the demo is attempting
to connect to the server?

-- Nathaniel

-- 
The Universe may  /  Be as large as they say
But it wouldn't be missed  /  If it didn't exist.
  -- Piet Hein

This email may be read aloud.