Description of problem: On a clean Fedora 32 Workstation with a clean Firefox profile, Firefox starts in a window that is not maximized neither normal ("non-maximized"). The window doesn't cover the whole screen, but its borders "look" like maximized (there are no shadows, no curved corners), and the window can't be resized. By dragging the title bar or a double click, the window can be reset into normal state (however, it partially jumps offscreen to the right when you do that). Then you can maximize it with another double click or by pulling it to the top GNOME bar. You can use it regularly then. But once you quit Firefox when maximized and start it again, the problem repeats - again you see a cropped window that is neither normal nor maximized and can't be resized. This only happens on Wayland. On X11, this works fine. Version-Release number of selected component (if applicable): firefox-74.0.1-3.fc32.x86_64 gnome-session-wayland-session-3.36.0-2.fc32.x86_64 gnome-shell-3.36.1-2.fc32.x86_64 gtk3-3.24.16-1.fc32.x86_64 libwayland-client-1.18.0-1.fc32.x86_64 libwayland-cursor-1.18.0-1.fc32.x86_64 libwayland-egl-1.18.0-1.fc32.x86_64 libwayland-server-1.18.0-1.fc32.x86_64 mutter-3.36.1-3.fc32.x86_64 xorg-x11-server-Xwayland-1.20.8-1.fc32.x86_64 How reproducible: always Steps to Reproduce: 1. boot F32 Workstation, log in under Wayland 2. $ rm ~/.mozilla/ ~/.cache/mozilla/ -rf # warning, this will erase all firefox data 3. run Firefox 4. depending on your resolution, either Firefox starts in "maximized" mode (but broken, as described here), or normal mode 5. maximize Firefox 6. close and start Firefox again 7. Firefox should again be in a broken window state, as described
Created attachment 1676934 [details] bug demonstration video This video demonstrates the problem.
Created attachment 1676935 [details] screenshot in 1920x1080 In 1920x1080, the problem is even more visible, because "maximized" Firefox window occupies only around half the screen.
Proposing as an F32 Final blocker, because either Firefox or the windowing system doesn't work correctly, preventing users from using maximized applications comfortably.
This is https://gitlab.gnome.org/GNOME/gtk/-/issues/2538 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623658)
Hello Jonas, you implemented the fix in gtk for this. Do you think we can get a fixed gtk version in Fedora 32 in the next few days? Or should I bother somebody else? Thanks.
It was included in https://bodhi.fedoraproject.org/updates/FEDORA-2020-8ced3e4e6b which was unpushed due to regressions. It'll be available in 3.24.18 which will happen relatively soon I think.
*** Bug 1815127 has been marked as a duplicate of this bug. ***
I'm at least +1 FE on this, for the record.
FEDORA-2020-ac3dfd7904 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ac3dfd7904
FEDORA-2020-ac3dfd7904 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ac3dfd7904` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ac3dfd7904 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-ac3dfd7904 fixes the issue. Firefox now starts maximized even if it was closed as not-maximized window previously, but if this is a bug at all, it is a different issue.
Discussed during the 2020-04-13 blocker review meeting: [0] The decision to delay the classification of this bug as a blocker and accept it as an "AcceptedFreezeException" was made as it's a close call whether this is bad enough to be a blocker and we don't have a clear decision on that, but we definitely accept it as an FE and the update to fix it has strong positive feedback, so we expect to push that and resolve the bug. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-04-13/f32-blocker-review.2020-04-13-16.04.txt
FEDORA-2020-ac3dfd7904 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.