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 683155 - OS X Quartz build fails to bring plugin windows to foreground
OS X Quartz build fails to bring plugin windows to foreground
Status: RESOLVED DUPLICATE of bug 677776
Product: GIMP
Classification: Other
Component: User Interface
2.8.2
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-09-01 12:23 UTC by Richard van den Berg
Modified: 2012-09-14 08:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Richard van den Berg 2012-09-01 12:23:48 UTC 
I've downloaded gimp-2.8.2-dmg-2.dmg but the About window says Gimp 2.8.3. Gimp starts fine, but when using File -> Open, selecting any file makes the Open dialog unresponsive, and the image is never shown on the canvas. The X11 version of 2.8.2 is working fine (OS X Mountain Lion version).
Comment 1 Clayton Walker 2012-09-01 16:16:35 UTC 
Did you have a look in the dock? There should be another icon there (representing the plugin). Currently, these don't automatically come to the foreground, and therefore must be explicitly clicked on to bring to the foreground. Most likely the plugin was attempting to ask you if the image was rotated, or if you wanted to convert color profiles etc.
Comment 2 Richard van den Berg 2012-09-01 22:05:21 UTC 
Thanks, that was it. A dialog about the color profile opened in the background. The strange thing is, there was no such dialog using the X11 version. I checked the Color Management preferences, and in both versions "File Open behaviour" is set to "Ask what to do".

It seems more dialogs seem to open behind the canvas, for example: File -> Properties
Comment 3 Michael Natterer 2012-09-14 08:37:54 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 677776 ***