Created attachment 1951693 [details] Screenshot of Fedora 38 Beta Description of problem: Titlebars increase in size and have a frame around them when using a gtk theme such as Materia-dark and swapping to another variant such as Materia-light or plain Materia. This is also tested with Breeze and swapping to another theme. Applications with headerbars update correctly. This was tested under Budgie Desktop with Budgie Desktop Settings being used to change the theme. This issue does not exist under Fedora 37. Version-Release number of selected component (if applicable): mutter-44~rc-4.fc38 How reproducible: Steps to Reproduce: 1. Grab Fedora 38 Budgie Spin beta image 2. Open up an application such as the file manager (Nemo). 3. Open up Budgie Desktop Settings, switch widget theme. 4. Notice titlebars are broken while applications with headerbars such as Budgie Desktop Settings or gedit work fine. Actual results: Broken theming Expected results: No broken SSDs. Additional info:
Does it help if you make the frame decoration process use the cairo renderer? You need to manually recompile to test.
Does it still look incorrect if you relogin after changing the theme?
(In reply to Jonas Ådahl from comment #1) > Does it help if you make the frame decoration process use the cairo > renderer? You need to manually recompile to test. I'll take a look at doing that as soon as possible and get back to you on that. (In reply to Jonas Ådahl from comment #2) > Does it still look incorrect if you relogin after changing the theme? Unfortunately yes, after a relog post-change it is still looking incorrect.
I am not seeing anything in meson_options for this. Is this not a configure-time option? If not, what would I need to be reverting locally to facilitate this?
This is still broken, I'm getting user complaints about it and I'm concerned about the damage this will cause to the image of Fedora Budgie Spin due to the failed inconsistencies in Mutter 44 related to this. What can we do about this issue? Can I get a reply to comment 4 please?
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 '38'. 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 38 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.
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.