GNOME Bugzilla – Bug 776294
Screenshot buttons cannot be clicked
Last modified: 2016-12-28 15:57:50 UTC
None of the buttons in the "File > Create > Screenshot" popup can be clicked. Neither the radio buttons nor the "Help," "Cancel," and "Snap" buttons. OSX can close the window with the top-left (x). I'm using macOS Sierra v10.12.1
Hello, Thanks for reporting. We'll need to wait for Kris or some other OSX dev to look into this issue, I guess. > Neither the radio buttons nor the "Help," "Cancel," and "Snap" buttons. Which buttons are these exactly?
It works for me on my machine with 10.9. Will also try on my 10.11 machine, if it works fine on that machine too it could be an issue with Sierra.
Also works on 10.11. We need to figure out whether this is an issue that only appears on Sierra. It could be that this is caused by the new tab behavior introduced in Sierra. Perhaps you can try and see what happens if you disable the "Prefer tabs when opening documents:" option under System Preferences > Dock.
Your suspicions were correct. My tab preferences on Sierra had been set to "In Full Screen Only," but after changing it to "Manually," the screenshot dialog works again.
Thanks for the quick reply! I think the best we can do right now is to disable this behavior for GIMP (GIMP can opt-out from the automatic tab behavior), so GIMP will at least work properly on Sierra. Will be looking into a patch.
I think this should fix it ... Committed to master and gimp-2-8. commit 7c35d75bf9e540408eb3a6b835f31d82a49d07b1 Author: Kristian Rietveld <kris@loopnest.org> Date: Wed Dec 28 16:12:33 2016 +0100 Bug 776294 - Screenshot buttons cannot be clicked Disable the new "automatic window tabbing" feature introduced on macOS Sierra. It breaks GTK+ applications and we would need proper support for this in GTK+ if we want to use it.
For now, we have fully disabled automatic window tabbing. I think that we should be respecting the user setting for this in Sierra in the future. Discussion on this feature will take place in bug 776546.
(and actually close the bug, forgot to do this together with the commit message.)
*** Bug 773677 has been marked as a duplicate of this bug. ***