GNOME Bugzilla – Bug 121412
Seg fault on scrolling through fonts with the font selection tool.
Last modified: 2004-12-22 21:47:04 UTC
When using the script-fu font selector and roaming through the list quicky or for non short periods of time...gimp seems to die on me...Doesn't look a good bug. If there's such a thing. (gimp-1.3:13279): Gtk-WARNING **: Invalid input string moving plug-in translation to trash: <Image>/Script-Fu/Stencil Ops/C_arve-It... moving plug-in translation to trash: <Image>/Script-Fu/Utils/ASCII to Image Layer... ** (gimp-1.3:13279): WARNING **: Unable to load unicode charmap from font file /usr/share/fonts/ja/TrueType/wadalab-gothic.ttf ** (gimp-1.3:13279): WARNING **: Unable to open font file /usr/share/fonts/ja/TrueType/wadalab-gothic.ttf for font WadaLab Gothic 21. 3330078125, falling back to /usr/X11R6/lib/X11/fonts/100dpi/UTBI__10-ISO8859-1.pcf.gz ** (gimp-1.3:13279): WARNING **: Error in FT_Set_Char_Size: 23 ** (gimp-1.3:13279): WARNING **: Unable to load unicode charmap from font file /usr/share/fonts/ja/TrueType/watanabe-mincho.ttf ** (gimp-1.3:13279): WARNING **: Unable to open font file /usr/share/fonts/ja/TrueType/watanabe-mincho.ttf for font Watanabe Mincho 21.3330078125, falling back to /usr/X11R6/lib/X11/fonts/100dpi/UTBI__10-ISO8859-1.pcf.gz ** (gimp-1.3:13279): WARNING **: Error in FT_Set_Char_Size: 23 gimp-1.3: fatal error: Segmentation fault gimp-1.3 (pid:13279): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s
+ Trace 39953
[netstar@localhost netstar]$ Hope this helps!
What version of Pango are you using? Looks like a Pango bug to me.
Could you please also change the summary of this report to something more sensible. Thanks.
We cannot do anything about this report w/o detailed information about Pango and Freetype version. Unless there is feedback from the bug-reporter during the next days, this report will have to be closed as INCOMPLETE.
The version information you requested is as follows: pango Version 1.2.3 freetype-2.1.5rc2
Thanks for the information you provided. Looks like one of those problems with unusual font configurations combined with the problem described in bug 101856. It seems a non-scaleable font is choosen as the fallback and Pango chokes on FT_Set_Char_Size(). I will investigate this problem.
*** This bug has been marked as a duplicate of 120095 ***