After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 135121 - GIMP crash on text-tool properties font selection
GIMP crash on text-tool properties font selection
Status: RESOLVED DUPLICATE of bug 101856
Product: GIMP
Classification: Other
Component: Tools
1.x
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-02-22 15:17 UTC by Lucas Langa
Modified: 2004-02-22 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lucas Langa 2004-02-22 15:17:43 UTC
Using The GIMP 2.0-pre2 (GTK+ 2.2.4-2) from Jernej Simoncic's page. I
encounter such behaviour: 1. open The GIMP; 2. select the text-tool; 3.
open its properties; 4. select the font selection dialog (this Aa icon); 5.
scroll down to see other fonts; 6. crash

I managed to gather some debug information. The GIMP crashes immediately
but if you open a large image then it closes itself a little bit longer
allowing to make at least a screenshot of the messages. Here they go:

** (gimp-1.3.exe:3332): WARNING **: [Invalid UTF-8] Unable to open font
file C:\WINDOWS\fonts\Sp#ywaj.ttf for font Sp##ywaj 16, falling back to
C:\WINDOWS\fonts\webdings.ttf

** (gimp-1.3.exe:3332): WARNING **: Unable to load unicode charmap from
file C:\WINDOWS\fonts\webdings.ttf, exiting

First of all, Poland uses Central European character sets such as
ISO-8859-2 or CP-1250. It is Latin but with some enhancement sings. A hash
# represents a corrupted sign which was in the place of a polish special
sign. So the bug is probably caused by this.
Moreover, I decided to delete all fonts with polish signs from
C:\WINDOWS\FONTS\ since The GIMP is just so cool BUT still I get exactly
the same message concerning Sp#ywaj.ttf which I deleted successfully.

About the second warning: there are some fonts which do not have any
alphabetical characters (these are used with the Windows GUI, represent
musical notes or glyphs, etc.) so they should be handled without crashing.

Still I don't actually know which of the two reasons matters most. Good luck.

Regards,
Lucas 'kSh' Langa
Comment 1 Sven Neumann 2004-02-22 15:48:27 UTC
Someone should finally install a proper fallback for symbol fonts on
Win32. Apart from that, this is yet another duplicate of bug #101856.

*** This bug has been marked as a duplicate of 101856 ***