FinalBlocker +1

FinalBlocker +1

This breaks the Fedora branding and as such should be considered a blocker.

Violation of the self identification criteria.

FinalBlocker +1

FinalBlocker +1
Fedora branding

I've added some more info to this:
https://bugzilla.redhat.com/show_bug.cgi?id=2444046#c6

I find having this as a release blocker quite unreasonable. It all looks correctly in a default state. If you enable dark mode inside a user session, the bug again doesn't manifest with default values ("Desktop and window layout" checkbox is disabled by default). Only if you enable dark mode in initial setup, then the button is different yes, but still working correctly, and most people won't even realize the image could have been different. It also has a trivial workaround, just switch themes, while checking "Desktop and window layout". Come on, this is just a visual nitpick.

https://fedoraproject.org/wiki/Basic_Release_Criteria#Self-identification is not violated, the button doesn't communicate any version etc.

https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria#First_boot_experience is not really violated, it works as intended. Toggling the dark mode works properly. The problem is not in initial setup, it's in the theme.

https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria#Default_panel_functionality is not violated, everything functions properly. Yes, the branding is not there, but it has no functionality downsides, and many people won't even be aware of the logo difference.

https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria#Default_application_functionality could be violated for system settings, in a conditional state where initial setup is used to toggle it, or when the user enables non-default options ("Desktop and window layout" when going to the dark mode). Is this still a "basic functionality test"? And is the consequence severe enough? I don't think so.

FinalBlocker -1

There's also "The proposed final Fedora artwork must be included and used as the background on release-blocking desktops. All Fedora artwork visible in critical path actions on release-blocking desktops must be consistent with the proposed final theme" which we've used to cover this sort of thing before. But I think I agree with kparal:

FinalBlocker -1

AGREED RejectedFinalBlocker AcceptedFinalFreezeException

Discussed at the 2026-03-16 (blocker / freeze exception) review meeting:

There are differing opinions on this, but we noted that the existing criteria were written for 'artwork' that changes per-release and were not meant to cover permanent branding issues. There's some support for adding branding criteria, but the narrow consensus was this is probably a minor enough issue that it shouldn't constitute a blocker even if we do write branding criteria. We're open to reconsidering this if a broad swell of folks who weren't present at the meeting are concerned. It's accepted as an FE as a visible issue in a blocking desktop that can't be resolved with an update.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-16/f44-blocker-review.2026-03-16-16.01.log.txt

The following votes have been closed:

• Rejected FinalBlocker (+4, 0, -2)
  • +1 by derekenz, asciiwolf, nielsenb, psklenar
  • -1 by kparal, adamwill
• Accepted FinalFreezeException (+0, 0, -0)

Release F44 is no longer tracked by BlockerBugs, closing this ticket.