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 725028 - Eyedropper tool problems
Eyedropper tool problems
Status: RESOLVED DUPLICATE of bug 676708
Product: GIMP
Classification: Other
Component: General
2.8.10
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-02-23 23:40 UTC by jytran85
Modified: 2014-02-24 00:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Eyedropper tool picture (88.72 KB, image/png)
2014-02-23 23:40 UTC, jytran85 		Details

Description jytran85 2014-02-23 23:40:02 UTC 
Created attachment 270080 [details]
Eyedropper tool picture

Bug:
Main eyedropper tool works fine from the Toolbox - Tool Options bar. The main problem is within the "Change Foreground Color" screen eyedropper. I installed GIMP with my primary display being the left side monitor (I have 2 monitors). Eyedropper tool within this was working fine until I switched my main display to the right hand monitor. After doing that, the eyedropper tool would not select any colour. It would either return black or white. I switched the display back to how it was when I first installed it and it went back to normal.


Seems like the bug eyedropper tool in the "Change Foreground Color" screen goes all wonky if original installation screen settings are changed.
Comment 1 Michael Schumacher 2014-02-24 00:01:10 UTC 
Duplicate of bug 676708?
Comment 2 jytran85 2014-02-24 00:05:56 UTC 
Whoops, I completely missed that bug. Sorry for wasting your time Michael. You can close this one off.
Comment 3 Michael Natterer 2014-02-24 00:43:15 UTC 
Thanks for the bug report. 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 676708 ***