Bug 2307728
| Summary: | gtk4 4.15.5 breaks display change confirmation dialog on X11 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joshua Strobl <joshua> | ||||||||
| Component: | gtk4 | Assignee: | GNOME SIG Unassigned <gnome-sig> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 41 | CC: | awilliam, fzatlouk, gnome-sig, klember, mclasen, ngompa13, suraj.ghimire7, y9t7sypezp | ||||||||
| Target Milestone: | --- | Keywords: | Desktop | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | AcceptedFreezeException | ||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2025-12-16 17:09:13 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 2247866 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Joshua Strobl
2024-08-24 17:49:21 UTC
Proposed as a Freeze Exception for 41-beta by Fedora user joshstrobl using the blocker tracking app because: There will need to be a freeze exception for any gtk4 release pre-emptively in the event this is fixed upstream. gtk4 4.15.5 breaks Budgie's confirmation prompt for display change confirmation, whereas 4.15.4 does not. Created attachment 2044826 [details]
screenshot after clicking "Apply" in "Displays" dialog
Reliably reproducible with Fedora-Budgie-Live-x86_64-41-20240824.n.0.iso in a VM.
No rebooting is required. Simply wait for the confirmation dialog to time out. And then run another test.
(In reply to Joshua Strobl from comment #0) < gtk4-4.15.4-1.fc41.x86_64 > gtk4-4.15.5-1.fc41.x86_64 gtk4-4.15.5 also breaks F41 Workstation with gnome-session-xsession installed and selected at login. Procedure: Install and update F41 Workstation in a VM. Install gnome-session-xsession and reboot. Select login name. Click on the gear icon and select "GNOME on Xorg". Login. Open a terminal or the settings manager. With gtk4-4.15.5 no windows are displayed, and there are various display artifacts. With gtk4-4.15.4 the display appears as expected. Download gtk4-4.15.4 from here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2521180 (In reply to Steve from comment #3) > gtk4-4.15.5 also breaks F41 Workstation with gnome-session-xsession installed and selected at login. This is, admittedly, contrived, but I can break F41 Workstation Live by installing gnome-session-xsession, configuring a password for liveuser, and logging out. The rest of the procedure is the same as in Comment 3. Tested with: Fedora-Workstation-Live-x86_64-41-20240824.n.0.iso Joshua: Could you update the bug title to reference 4.15.5 instead of 4.15.4? Upstream issue status indicates this was fixed with https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7633 ? I've backported that in https://bodhi.fedoraproject.org/updates/FEDORA-2024-08b2a6e32d . If you could test and confirm whether that fixes it, that would be great. Created attachment 2044889 [details] screenshot with F41 Workstation and gtk4-4.15.5-2 gtk4-4.15.5-2 doesn't quite fix the rendering problem when running my F41 Workstation test case from Comment 3. Sometimes the terminal window is rendered correctly and sometimes it is not. As the screenshot shows, the terminal is functional. $ rpm -q gtk4 gnome-session-xsession gtk4-4.15.5-2.fc41.x86_64 gnome-session-xsession-46.0-3.fc41.x86_64 Discussed during the 2024-08-26 blocker review meeting: [1] The decision to classify this bug as a AcceptedFreezeException (Beta) was made: "This is accepted as it breaks significant functionality on non-release-blocking desktops (including Budgie). we will check with GTK folks that the fix should be safe before landing it." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-08-26/f41-blocker-review.2024-08-26-16.00.log.html gtk4-4.15.5-2.fc41.x86_64 also breaks the GNOME and GNOME Classic sessions. The terminal window is not rendered correctly, although it is functional. To be sure there is no interaction, I removed gnome-session-xsession and rebooted. $ rpm -q gtk4 gnome-session-xsession gtk4-4.15.5-2.fc41.x86_64 package gnome-session-xsession is not installed GNOME: $ env | sort | egrep 'XDG_CURRENT_DESKTOP|XDG_SESSION_DESKTOP|XDG_SESSION_TYPE' XDG_CURRENT_DESKTOP=GNOME XDG_SESSION_DESKTOP=gnome XDG_SESSION_TYPE=wayland GNOME Classic: $ env | sort | egrep 'XDG_CURRENT_DESKTOP|XDG_SESSION_DESKTOP|XDG_SESSION_TYPE' XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME XDG_SESSION_DESKTOP=gnome-classic XDG_SESSION_TYPE=wayland (In reply to Steve from comment #10) > gtk4-4.15.5-2.fc41.x86_64 also breaks the GNOME and GNOME Classic sessions. Human testers can't beat the machine: :-) https://openqa.fedoraproject.org/tests/2820005#step/desktop_terminal/4 yikes, okay. let's revert that, then. Created attachment 2044939 [details]
screenshot with gtk4-4.15.6-1 in GNOME session
Moving the pointer around will refresh various dialog components.
Resize pointer is visible at upper right.
Resizing triggers a complete refresh.
Tested with:
$ rpm -q gtk4 gnome-control-center
gtk4-4.15.6-1.fc41.x86_64
gnome-control-center-47~beta-1.fc41.x86_64
$ env | sort | egrep 'XDG_CURRENT_DESKTOP|XDG_SESSION_DESKTOP|XDG_SESSION_TYPE'
XDG_CURRENT_DESKTOP=GNOME
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
Could someone add this to the upstream links? Initial rendering gone missing in Fedora 41 vm https://gitlab.gnome.org/GNOME/gtk/-/issues/6964 Aside from demonstrating the bug, this screencast is a thing of beauty: :-) https://gitlab.gnome.org/-/project/665/uploads/9d9d56c6c421508bf571c88f89776162/Screencast_From_2024-08-27_09-51-21.mp4 Well, really, that bug is different. That bug is caused by the attempted *fix* for this bug. I wasn't referring to the mesa bug. Anyway, as far as testing goes, what are we waiting for ATM? gtk4-4.15.7 or a mesa update? 4.15.7 would be nice, or we can try backporting https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7662 and https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7663 . Ugh, so now we have a 4.16.0 with a bunch of other changes, and git is already bumped to that, so I can't build a 4.15.5 or 4.15.6 with specifically targeted backports, as we should do during freeze. :( We either have to live with this or go to 4.16.0. Is going with the known good 4.15.4 (at least, it resolves the issue I filed) not an option and leave the experimenting of other changes to rawhide, with a backport to 41 when all validation passes? "Living with this" will mean breaking display configuration applying for Budgie users and those that upgrade from 40 to 41 will go from having a functional display configuration applying to it being broken. Not something I would want users to just live with. I'm only talking about the beta, here. For final we'll likely go with 4.16.x. Understood. For beta in the case of the Budgie issue, it's acceptable for it to be broken and I can field questions on that should they come up and I see them. Now whether or not the issues Steve raised on issues on the GNOME session are seen as acceptable being broken (hopefully temporarily =) ) during beta is another question. Those won't be broken in beta, because we did not push any build that causes those bugs to stable. I've just unpushed the 4.15.6 update so people will also not get it on update. This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '41'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15. Fedora Linux 41 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |