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 772429 - Crash when color-picking from Color Exchange dialog
Crash when color-picking from Color Exchange dialog
Status: RESOLVED DUPLICATE of bug 740634
Product: GIMP
Classification: Other
Component: Plugins
2.8.18
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-10-04 21:29 UTC by RrnR
Modified: 2016-10-09 22:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screen shot of crash error message (12.54 KB, image/png)
2016-10-04 21:29 UTC, RrnR 		Details

Description RrnR 2016-10-04 21:29:00 UTC 
Created attachment 336956 [details]
screen shot of crash error message

Steps to reproduce:

 - In Explorer right-mouse click on a PNG file, choose "Edit with Gimp"
 - In Layer window, right-click layer and select "Duplicate layer"
 - select duplicated layer
 - select Colors/Map/Color Exchange 
 - Choose the "From" color by middle clicking on the preview image
 - click the "To" color to open the color dialog
 - click on the color picker button
 - click on the thumbnail of an image file in Windows Explorer

Boom! https://dl.dropboxusercontent.com/u/311035/Gimp%20color%20exchange%20crash.png

The above are what I did to reproduce the crash. I haven't experimented to see what the minimum steps needed are.
Comment 1 RrnR 2016-10-05 08:01:02 UTC 
After browsing the suggested similar issues, I offer additional info that might be relevant. I run three monitors - left:1920x1200, centre (main): 1920x1200, right: 1680x1050.  When the error occurred the Color Exchange dialog was displayed in the centre monitor and I was clicking the eyedropper on the left-hand monitor.
Comment 2 Michael Natterer 2016-10-09 22:36:24 UTC 
Thanks, will paste that info to the original bug.

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