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 623060 - Program crashes when Using Text Tool
Program crashes when Using Text Tool
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-28 19:06 UTC by glow.bugz01
Modified: 2010-06-28 19:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description glow.bugz01 2010-06-28 19:06:22 UTC 
I download Gimp 2.6.9 the other day. When using the text tool and trying to select a new font the program crashes.

I am running Windows 7 Home premium 64 bit.

I had Gimp 2.6.8 installed. Had no problems with the text tool.
Uninstalled Gimp 2.6.8.
Restarted computer.

Installed Gimp 2.6.9
Opened Gimp
New image.
Went to try putting text on a path. 
Created path.
Clicked on text tool.
Clicked to open drop down list of fonts.
Tried to scroll on font drop down list.
Gimp crashed.

Restarted computer.
Opened Gimp.
New image.
Clicked on text tool.
Clicked to open drop down list of fonts.
Tried to scroll on font drop down list.
Gimp crashed.

Opened Gimp.
New Image.
Clicked on text tool.
Clicked to open drop down list of fonts.
Clicked on a font. (did not try to scroll)
Typed out text.

When opening Gimp on load screen I did not see the fonts being loaded.

Uninstalled Gimp 2.6.9.
Restarted Computer.

Reinstalled Gimp 2.6.8.
Opened Gimp.
New Image.
Clicked on text tool.
Clicked to open font drop down list.
Scrolled and clicked on font. (works fine)
Typed out text. 

Know of another person having problems with text tool in Gimp 2.6.9.

Tammie
Comment 1 Michael Schumacher 2010-06-28 19:07:31 UTC 
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 ***