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 743712 - Crash when i'm trying to change font
Crash when i'm trying to change font
Status: RESOLVED DUPLICATE of bug 743717
Product: GIMP
Classification: Other
Component: Tools
2.8.14
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-01-29 21:21 UTC by fabryx92
Modified: 2016-04-17 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Mac OS Problem Reporter result (125.85 KB, application/pdf)
2015-01-29 21:21 UTC, fabryx92 		Details
Mac OS Problem Reporter result (without opening image first) (111.87 KB, application/pdf)
2015-01-29 21:24 UTC, fabryx92 		Details

Description fabryx92 2015-01-29 21:21:38 UTC 
Created attachment 295779 [details]
Mac OS Problem Reporter result

I do this things:
- open gimp first
- go to mac os finder and open an image using "open with.."
- click on color picker and select a color
- create text area and write something
- click a bit of times on the selected font to try to change it 
- crash!

P.S. i notice that this occur too if gimp has just been launched without opening an image
Comment 1 fabryx92 2015-01-29 21:24:28 UTC 
Created attachment 295780 [details]
Mac OS Problem Reporter result (without opening image first)

this is the report created when gimp crashes without opening an image first, only typing on font to change it
Comment 2 Kristian Rietveld 2016-04-17 14:40:01 UTC 
I cannot really find a hint in the second backtrace, that perhaps indicates a GTK+ issue.

The first backtrace indicates to me that this is probably related to the clipboard issues that have been reported. I will resolve this bug as a duplicate of the general clipboard bug.


Could you tell us whether you were using a clipboard manager when you experienced this crash?

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