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 762532 - Instant crash when changing font sizes, layer sizes etc
Instant crash when changing font sizes, layer sizes etc
Status: RESOLVED DUPLICATE of bug 743717
Product: GIMP
Classification: Other
Component: User Interface
2.8.16
Other Mac OS
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-02-23 12:57 UTC by d.toule
Modified: 2016-03-30 22:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Gimp error report (62.34 KB, text/plain)
2016-02-23 12:57 UTC, d.toule
Details

Description d.toule 2016-02-23 12:57:41 UTC
Created attachment 321948 [details]
Gimp error report

I previously registered this error before as something that happens when I edit font sizes, but I've now realised it's actually any of these boxes (not sure what they're called). If I edit layer size, image size, font size - any of these, I get an instant crash and lose everything.

How can I fix this? Any help would be great, as it pretty much limits my use of GIMP!

Thanks a lot,

David
Comment 1 d.toule 2016-03-01 01:52:50 UTC
Does anyone have any suggestions? I just realised that even if I change opacity, GIMP crashes ... Please help!
Comment 2 Michael Schumacher 2016-03-01 06:47:12 UTC
Others definitely don't see this - any idea what could make your system or this case unique?
Comment 3 d.toule 2016-03-01 14:43:11 UTC
It's strange... Does the above error report give any clues?

Could anyone run through how I can fully delete GIMP on a mac and clear any temporary or cached files, so that I can do a full install?
Comment 4 Michael Natterer 2016-03-30 22:15:12 UTC
The attached stack trace shows that this is clearly another instance
of crashing when setting the PRIMARY clipboard.

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