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 764722 - Child window placement broken between gtk3.20.1 and gtk3.20.2
Child window placement broken between gtk3.20.1 and gtk3.20.2
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Win32
3.20.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-04-07 12:32 UTC by Ole Christian Eidheim
Modified: 2016-04-11 18:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ole Christian Eidheim 2016-04-07 12:32:43 UTC
On slower systems running MYS2 I see that child windows are now all placed on top left (0,0) position of the screen. This is reproducable by running "gtk3-demo/Dialogs and Message Boxes/Message Dialog" on a newly upgraded MSYS2 running a virtual Windows through for instance VirtualBox. When running MSYS2 on native Windows, window placement is sometimes correct, but not in all cases. So far experienced with all dialogs, tooltips, and windows of type popup (normal window is not tested). 

This issue does not happen when I downgrade to gtk3 version 3.20.1.
Comment 1 Ignacio Casal Quinteiro (nacho) 2016-04-07 12:40:26 UTC
This should be fixed with this patch:
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-20&id=f233609c9328d03222a19e37db78caedb8b7e9c5

Thanks for reporting it.
Comment 2 Ignacio Casal Quinteiro (nacho) 2016-04-07 14:13:56 UTC
*** Bug 764730 has been marked as a duplicate of this bug. ***
Comment 3 Ole Christian Eidheim 2016-04-11 17:12:04 UTC
I applied the patch (https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-20&id=f233609c9328d03222a19e37db78caedb8b7e9c5) to MSYS2's gtk3.20.2 and the problem is still present.
Comment 4 Ole Christian Eidheim 2016-04-11 18:14:59 UTC
Although, the patch https://git.gnome.org/browse/gtk%2B/commit/?id=a91237d65e91cf7dc1581fabf9245ca89e988088 fixes this issue.