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 771958 - Copy Crashes GIMP on OS/X when Clipboard Managers running
Copy Crashes GIMP on OS/X when Clipboard Managers running
Status: RESOLVED DUPLICATE of bug 743717
Product: GIMP
Classification: Other
Component: General
2.9.4
Other Mac OS
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-09-25 21:01 UTC by Dan Thomas
Modified: 2016-09-27 13:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
runMcGimp-2.9 log (44.57 KB, text/plain)
2016-09-25 21:01 UTC, Dan Thomas 		Details

Description Dan Thomas 2016-09-25 21:01:11 UTC 
Created attachment 336234 [details]
runMcGimp-2.9 log

GIMP versions 2.8 through the latest 2.9.5 (McGimp) on OS/X will crash while doing a Copy when a clipboard manager, like the one in Keyboard Maestro, is running.

I've only experienced this when Keyboard Maestro is running (it's the only thing with a clipboard manager that I have), but I've read other people talk about having this issue with other clipboard managers.

Steps to reproduce:

1) Run Keyboard Maestro (free download from www.keyboardmaestro.com).
2) Run GIMP and open an image.
3) Copy the image (should not crash yet).
4) Switch to another application.
5) Switch back to GIMP.
6) Do another copy.
7) GIMP will terminate.

McGimp log is attached.

This can be reliably and consistently recreated, without fail (well, with fail, but you know what I mean), so if the above steps for some reason don't cause the issue, please let me know.
Comment 1 Michael Schumacher 2016-09-27 13:26:59 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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