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 772664 - On Wayland, windows containing GtkGLArea fail to maximize correctly
On Wayland, windows containing GtkGLArea fail to maximize correctly
Status: RESOLVED DUPLICATE of bug 771915
Product: gtk+
Classification: Platform
Component: Widget: GtkGLArea
3.22.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-10-09 20:00 UTC by kritphong
Modified: 2016-10-11 15:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test program (540 bytes, application/x-xz)
2016-10-09 20:00 UTC, kritphong 		Details

Description kritphong 2016-10-09 20:00:24 UTC 
Created attachment 337286 [details]
test program

On Wayland, windows that contain GtkGLArea do not maximize correctly. The window appears to enter maximized state, but it is not moved to the correct position. This doesn't happen with gtk+ <= 3.20.

Steps to reproduce:
1. Run the attached test program.
2. Maximize the window (eg. by pressing Alt+F10).
Comment 1 Olivier Fourdan 2016-10-10 11:24:25 UTC 
Works fine here with gtk+-3.22.1 and mutter-3.22.0

Which version do you use?
Comment 2 kritphong 2016-10-11 15:01:29 UTC 
I'm using gtk+-3.22.0 and mutter-3.22.0.
Comment 3 Olivier Fourdan 2016-10-11 15:09:20 UTC 
gtk+-3.22.1 has the fix for bug 771915 and bug 771561 so I reckon it's a dupe of those.

Can you try to reproduce with gtk+-3.22.1 ?
Comment 4 Olivier Fourdan 2016-10-11 15:10:22 UTC 
Dupe of bug 771915 to be precise (although bug 771915 and bug 771561 are related)
Comment 5 kritphong 2016-10-11 15:50:36 UTC 
Looks like it really is a dupe of bug 771915. I'm no longer able to reproduce the bug after upgrading to gtk+-3.22.1.
Comment 6 kritphong 2016-10-11 15:50:48 UTC 

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