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 771413 - calculator is cropped when "maximized" (on wayland)
calculator is cropped when "maximized" (on wayland)
Status: RESOLVED DUPLICATE of bug 764413
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2016-09-14 09:40 UTC by Kamil Páral
Modified: 2016-09-14 12:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bug demonstration video (2.10 MB, video/webm)
2016-09-14 09:40 UTC, Kamil Páral
Details

Description Kamil Páral 2016-09-14 09:40:29 UTC
Created attachment 335504 [details]
bug demonstration video

If I have the calculator in basic mode and try to maximize it (Super+Up, or drag to screen top border), the calculator is put into top left corner and is cropped very often. See the video. In my testing, it is always cropped when using super+up, and sometimes cropped when dragging to screen top border. Once it stops being cropped, close it and open it again to reproduce the issue again.

This happens under Wayland. Under X11, I don't seem to be able to "maximize" the calculator in any way. So maybe this is an gtk issue in wayland which allows non-resizable windows to be "resized" using certain operations?


gnome-calculator-3.21.90-1.fc25.x86_64
gnome-session-wayland-session-3.21.90-1.fc25.x86_64
gnome-shell-3.21.91-1.fc25.x86_64
gtk3-3.21.5-1.fc25.x86_64
libwayland-client-1.11.93-1.fc25.x86_64
libwayland-cursor-1.11.93-1.fc25.x86_64
libwayland-server-1.11.93-1.fc25.x86_64
mesa-libwayland-egl-12.0.2-1.fc25.x86_64
mutter-3.21.91-2.fc25.x86_64
qt5-qtwayland-5.7.0-2.fc25.x86_64
xorg-x11-server-Xwayland-1.18.4-5.fc25.x86_64
Comment 1 Olivier Fourdan 2016-09-14 09:48:50 UTC
That should be fixed upstream with the addition of min/max size in xdg-shell v6 as implemented in gtk+ and mutter
Comment 2 Kamil Páral 2016-09-14 10:13:57 UTC
Please tell me once there is a Koji build to test, thanks. 
(Should we reassign to a different component?)
Comment 3 Olivier Fourdan 2016-09-14 11:38:09 UTC
(In reply to Kamil Páral from comment #2)
> Please tell me once there is a Koji build to test, thanks.

It's merely a note in the bugzilla that this particular issue is already fixed upstream.

koji is Fedora, not sure it makes sense to link an upstream bug to downstream processes.

> (Should we reassign to a different component?)

Yes, but actually it's a dupe... Both bugs for gtk+ and mutter are closed now, doesn't make sense to keep a dupe opened just because Fedora, does it?

gtk+:   https://bugzilla.gnome.org/show_bug.cgi?id=764413
mutter: https://bugzilla.gnome.org/show_bug.cgi?id=770226

*** This bug has been marked as a duplicate of bug 764413 ***
Comment 4 Kamil Páral 2016-09-14 12:23:32 UTC
(In reply to Olivier Fourdan from comment #3)
> It's merely a note in the bugzilla that this particular issue is already
> fixed upstream.
> 
> koji is Fedora, not sure it makes sense to link an upstream bug to
> downstream processes.

Well what I wanted to say is that I can test it if there are Fedora builds available already (testing a fix should be relevant even to an upstream project:)). In the end, we all use some distribution. If this doesn't require further testing, no problem.

> Yes, but actually it's a dupe... Both bugs for gtk+ and mutter are closed
> now, doesn't make sense to keep a dupe opened just because Fedora, does it?

No. If it was an important bug, I would open a downstream bug to track it until it is fixed in Fedora.