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 623084 - Font Toolbox Selection Causes Gimp 2.6.9 to Crash
Font Toolbox Selection Causes Gimp 2.6.9 to Crash
Status: RESOLVED DUPLICATE of bug 622608
Product: GIMP
Classification: Other
Component: Tools
2.6.9
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-06-29 01:27 UTC by Jay F
Modified: 2010-06-29 07:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jay F 2010-06-29 01:27:04 UTC
Just upgraded 6/28/10 from 2.6  to 2.6.9 - Problem was.

While doing the following...
Opening a 640x480 jpg file (RGB, 1 layer)

Making very minor modifications to image...then drawing a dialogue balloon over
subject to convey message.  Used Ellipse tool to draw circle...used bucket fill tool to create solid white background for balloon.  Then used Free Select Tool to create "V" that leads up to balloon -  then used bucket fill tool to create solid white background.   All without any problem.


****Problem starts when I choose the Text Tool and then attempt to select a font other than the default "SANS".   Attempting to change font styles causes GIMP 2.6.9 to crash.

 ****Also, any attempt to use the scroll bar in the font toolbox drop down menu... or just attempting to click on any of those visible font styles in the drop down also cause GIMP 2.6.9  to crash.    This sudden shut down is consistent time after time when attempting to select any font other than the default "SANS".

As an added note, my version of XP Pro is patched only to SP2




AppName: gimp-2.6.exe	 AppVer: 0.0.0.0	 ModName: libgtk-win32-2.0-0.dll
ModVer: 2.16.6.0	 Offset: 0012903f
Comment 1 Michael Schumacher 2010-06-29 07:20:30 UTC
Choosing other fonts doesn't cause a crash for me. Triggering bug 622608 does.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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