Hello, I haven't seen this bug anywhere else so if this is my fault please excuse me for wasting your time. I have looked all over google, bugs.gentoo.org, freetype-2.1.3 realease notes and gentoo forums. When I updated my system from freetype-2.1.2 (not sure which -rxx exactly) my gnome2 apps started crashing. Here is a trace using gdb of a simple program (gtk-theme-switch2): $ gdb switch2 GNU gdb 5.3 (snip) This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)... (gdb) run Starting program: /usr/bin/switch2 (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (switch2:26579): Gtk-WARNING **: Unable to locate theme engine in module_path: "cleanice", (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x406e0b42 in TT_Load_Simple_Glyph () from /usr/lib/libfreetype.so.6 I tried reemerging it several times, going back to older version, reemerging the app, even updated my gnome-2.0.2 system to gnome-2.0.3. Happily it's time for a change so I'm now using KDE 3.1rc5. I tracked down that when I set GDK_USE_XFT=0 switch2 runs ok, but more complex (?) programs like xchat-1.9.7 pops up a server editor and when trying to connect it crashes with the same error message. Maybe xchat's overriding gdk_use_xft, not sure ... Eclipse doesn't run. Mozilla (1.2.1 compiled without gtk2 support) runs when gdk_use_xft is set to 0. And the strangest of all here is that KDE runs without any problems, perfect antialiasing with and without the bytecode interpreter (using the new autohinting code) and the smooth patches. Some make.conf info: CHOST="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon -pipe -O3 " ACCEPT_KEYWORDS="~x86" USE="dga evo gd ggz gtk2 gtkhtml libgda maildir mule mysql odbc pda ruby samba sasl sse xml -apm -cups -berkdb -slang -tetex -guile -gpm -scanner" Other programs related to fonts (giving this info as I updated xft and emerged fontconfig for the first time the same day I updated freetype). xfree-4.2.1-r2 xft-2.0.1-r1 fontconfig-2.1-r1
Oh, running a gcc-3.2.1 and glibc-2.3.1-r2 system btw :)
Are you using the latest ~ gtk/pango/glib ? You might want and try to disable the slighthint patch in pango-1.2.0 just to make sure. oh and it works just fine for me btw
Yup, I'm running a pretty standard ~x86 system here. GTK+-2.2.0, Glib-2.2.0, pango-1.2.0. I disabled the slighthint patch in pango and then in freetype, no change. Thinking of it, maybe I should recompile xfree ? It seg faults in /usr/lib/libfreetype and not /usr/X11R6/lib, but I have no other ideas.
OK, found it. I just remembered last night at about 2:00 am looking at emerge -ep xfree that emerge fontconfig has crashed in the end running fc-cache. Then I remembered I had a RedHat 8.0 system where I copied all my windows truetype fonts and it couldn't even start X. Conclusion: low quality truetype (or should I say crappy) fonts can crash gnome and other freetype using apps. Fontconfig doesn't ignore them and somehow the new freetype decided it had to go through all the fonts ... I'll recheck exactly which ones cause the problem and submit a bug report upstream.
I think 2.1.3 adds gzip compression support or such. Prob picked out a few of those, and hit a bug.
Actually, can you try to merge freetype: # RESTRICT="nostrip" BUILDDEBUG="yes" CFLAGS="-ggdb" CXXFLAGS="-ggdb" \ emerge freetype and try and track where it crashes ? Or at least what font is causing this, and pass it this way so I can try to fix it ?
I just ran strace fc-cache and tracked it. It's a font called bodt.ttf, 43kb. Probably made in Bulgaria :) I can send it to your e-mail, is that ok ?
bzip it, and attach to this bug if possible, thanks.
Created attachment 7202 [details] The famous font
I tried to backtrace it, but I cannot seem to see the problem currently :/ Robert, if you are bored at some stage, and want to debug this, I will appreciate.
Program received signal SIGSEGV, Segmentation fault. 0x401bb7ff in TT_Load_Simple_Glyph (load=0xbffff0d0) at /var/tmp/portage/freetype-2.1.3-r2/work/freetype-2.1.3/src/truetype/ttgload.c:370 370 *flag++ = c = FT_GET_BYTE(); flag is NULL, from the assigment above, FT_Byte* flag = (FT_Byte*)outline->tags; (gdb) p outline->tags $2 = 0x0 Checking flag for NULL and returning an error just makes it crash again somewhere else. This should be forwarded upstream.
whats the status here reporter , have things improved with current freetype/fontconfig ?
needinfo
works for me, sorry for the delay, i was away from town
close
