Re: GTK build crashes under X

[Jan Djärv]

Stephen Berman skrev:

> fc-cache: "/usr/X11R6/lib/X11/fonts/uni": skipping, looped directory detected
> fc-cache: "/opt/kde3/share/fonts/override": skipping, looped directory detected
> fc-cache: "/usr/lib/ooo-2.0/share/fonts": skipping, 0 fonts, 1 dirs
> fc-cache: "/usr/lib/ooo-2.0/share/fonts/truetype": skipping, 1 fonts, 0 dirs
> fc-cache: "/usr/lib/ooo-2.0/share/fonts/truetype": skipping, looped directory 
> detected
> fc-cache: "/usr/lib/jvm/java-1.5.0-sun-1.5.0_07/jre/lib/fonts": skipping, 8 
> fonts, 0 dirs
> fc-cache: "/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/fonts": skipping, 12 
> fonts, 0 dirs
> fc-cache: "/usr/X11R6/lib/Acrobat7/Resource/Font": skipping, 16 fonts, 1 dirs
> fc-cache: "/usr/X11R6/lib/Acrobat7/Resource/Font/PFM": skipping, 0 fonts, 0 dirs
> fc-cache: "/usr/X11R6/lib/Acrobat7/Resource/Font/PFM": skipping, looped 
> directory detected
> fc-cache: failed
>
> > What version of fontconfig do you have?  Mine (2.2.3 and 2.3.2 and 2.4.1) does
> > not have any FcObjectToPtr method.
>
> address@hidden:~> rpm -qi fontconfig
> Name        : fontconfig  Relocations: (not relocatable)
> Version     : 2.3.94      Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
> Release     : 18.4        Build Date: Sat 10 Jun 2006 01:52:44 AM CEST
> ...
>
>
> It turns out that the wxGTK package mentioned above was in fact
> responsible for Emacs segfaulting; after uninstalling the wxGTK rpm,
> the Emacs GTK build started under X with no problems, as before.  Do
> you have any idea what the problem could be, or any suggestion how to
> try tracking it down (if it is necessary to recompile pango or wxGTK
> with debugging enabled, I probably cannot do it any time soon).

You can see if there are any standard files wxGTK installs or modifies, like 
/etc/fonts/fonts.conf or some other font files.  The output from fc-cache does 
not look right (Can't save cache for "/usr/local/share/fonts") did you run it 
as root?  You seem to have duplicate entries in /etc/fonts/fonts.conf (all 
those looped directory messages), but I don't think that should cause any 
problems.

My best bet would be to recompile fontconfig with debugging enabled and see 
exactly what font it tries to find when it crashes.  But I think this is more 
of a Suse problem than an Emacs problem.

        Jan D.