2026-03-16 @ **16:00** UTC - Fedora 44 Blocker Review Meeting

Project Discussion
1

Hi folks! It’s time for a Fedora 44 blocker (and FE) review meeting! We have 3 proposed blockers and 3 proposed freeze exception for Final.

PLEASE REMEMBER THE CHANGED MEETING TIME IN UTC, as noted last
week!

Here is a handy link which should show you the meeting time in your local time.

The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing.

If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here.

Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you’ll see links labeled “Vote!” next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. Making sure you're not a bot! has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn’t a clear outcome in the ticket voting yet. THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!

We’ll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they’re not fixed. Information on the release criteria for F44 can be found on the wiki.

For more information about the Blocker and Freeze exception process,
check out these links:

And for those of you who are curious how a Blocker Review Meeting works - or how it’s supposed to go and you want to run one - check out the SOP on the wiki.

Have a good day and see you tomorrow!

1 Like
2

#blocker-review:fedoraproject.org: F44-blocker-review

Meeting started by @adamwill:fedora.im at 16:01:48 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:01:52)
    1. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:07:04)
    2. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:07:04)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:07:04)
    1. LINK: https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria (@adamwill:fedora.im, 16:07:04)
    2. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:07:04)
    3. INFO: Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (@adamwill:fedora.im, 16:07:04)
    4. LINK: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria (@adamwill:fedora.im, 16:07:04)
    5. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:07:04)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:07:04)
    7. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:07:04)
    8. INFO: for Final, we have: (@adamwill:fedora.im, 16:07:18)
    9. INFO: 4 Accepted Blockers (@adamwill:fedora.im, 16:07:19)
    10. INFO: 3 Proposed Blockers (@adamwill:fedora.im, 16:07:19)
    11. INFO: 3 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:07:24)
    12. INFO: 1 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:07:24)
    13. INFO: Lukáš Růžička will secretarialize (@adamwill:fedora.im, 16:08:28)
  3. TOPIC:proposed Final blockers (@adamwill:fedora.im, 16:08:42)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2444824 (@adamwill:fedora.im, 16:08:48)
    2. INFO: Ticket vote: FinalBlocker (+1,0,-1) (+asciiwolf, -nielsenb) (@adamwill:fedora.im, 16:08:48)
    3. INFO: Proposed Blocker, pipewire, POST (@adamwill:fedora.im, 16:08:48)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2071 (@adamwill:fedora.im, 16:08:48)
  4. TOPIC:(2444824) GNOME Remote Desktop (RDP remote login) connects but shows a blank white screen and disconnects shortly afterwards (Fedora 44). (@adamwill:fedora.im, 16:08:48)
    1. AGREED: 2444824 - punt (delay decision) on blocker status, AcceptedFreezeException (Final) - this is accepted as a freeze exception issue as the GNOME remote desktop case is definitely heavily broken and we want that fixed for release if possible. Blocker status decision is delayed as the blocker case (RDP install) seems to fail much less often, but we want to investigate more thoroughly before deciding (@adamwill:fedora.im, 16:29:16)
  5. TOPIC:(2444046) Incorrect KDE application launcher icon when user configures dark mode during initial setup (@adamwill:fedora.im, 16:29:26)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2444046 (@adamwill:fedora.im, 16:29:26)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2076 (@adamwill:fedora.im, 16:29:26)
    3. INFO: Proposed Blocker, plasma-setup, NEW (@adamwill:fedora.im, 16:29:26)
    4. INFO: Ticket vote: FinalBlocker (+4,0,-2) (+derekenz, +asciiwolf, +nielsenb, +psklenar, -kparal, -adamwill) (@adamwill:fedora.im, 16:29:26)
    5. AGREED: 2444046 - RejectedBlocker (Final) AcceptedFreezeException (Final) - 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 re-considering 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 (@adamwill:fedora.im, 17:01:42)
    6. INFO: Ticket vote: FinalFreezeException (+4,0,-0) (+asciiwolf, +nielsenb, +derekenz, +adamwill) (@adamwill:fedora.im, 17:02:54)
    7. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2391723 (@adamwill:fedora.im, 17:02:54)
  6. TOPIC:(2391723) `shim-ia32` missing since `shim-15.8-4` (@adamwill:fedora.im, 17:02:54)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2075 (@adamwill:fedora.im, 17:02:54)
    2. INFO: Proposed Blocker, shim, NEW (@adamwill:fedora.im, 17:02:54)
    3. INFO: Ticket vote: FinalBlocker (+2,0,-0) (+nielsenb, +derekenz) (@adamwill:fedora.im, 17:02:54)
    4. AGREED: 2391723 - AcceptedBlocker (Final) - this is accepted as a violation of "All release-blocking images must boot in their supported configurations" in the case of x86_64 systems with 32-bit UEFI firmwares. our subjective decision was that this is a significant enough class of systems to constitute a release blocking bug. Note we accept this only in the context of 'making an effort to support such systems', as the fix is relatively straightforward. We don't necessarily intend to establish a precedent that any kind of bug in this unusual path becomes a blocker; one that required more work by the developers may not reach the bar. (@adamwill:fedora.im, 17:21:14)
  7. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 17:21:30)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2064 (@adamwill:fedora.im, 17:21:36)
    2. INFO: Ticket vote: FinalFreezeException (+2,0,-0) (+asciiwolf, +nielsenb) (@adamwill:fedora.im, 17:21:36)
    3. INFO: Ticket vote: FinalBlocker (+2,0,-1) (+nielsenb, +derekenz, -kparal) (@adamwill:fedora.im, 17:21:36)
    4. INFO: Proposed Freeze Exceptions, dnf5, POST (@adamwill:fedora.im, 17:21:36)
  8. TOPIC:(2443774) dnf cli segmentation faults during transaction when locale is set to C or POSIX (@adamwill:fedora.im, 17:21:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2443774 (@adamwill:fedora.im, 17:21:36)
    2. AGREED: 2443774 - AcceptedFreezeException (Final) - this is accepted as an FE issue as it could affect folks on first update and require a workaround, but we will evaluate any proposed fix during freeze for its risk of affecting more important paths and only take a sufficiently safe fix. (@adamwill:fedora.im, 17:25:27)
  9. TOPIC:Accepted Final blocker review (@adamwill:fedora.im, 17:25:56)
    1. INFO: remember, we are just checking in on status here, not re-voting unless it's necessary for some reason (@adamwill:fedora.im, 17:26:07)
    2. INFO: three of the blockers are network installer image sizes. I did a quick investigation and didn't find any low-hanging fruit to target - https://bugzilla.redhat.com/show_bug.cgi?id=2431863#c9 . I will propose bumping the size limits soon (@adamwill:fedora.im, 17:26:56)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2359799 (@adamwill:fedora.im, 17:27:43)
    4. INFO: Accepted Blocker, mesa, NEW (@adamwill:fedora.im, 17:27:43)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2074 (@adamwill:fedora.im, 17:27:43)
  10. TOPIC:(2359799) Inital-setup: VK_ERROR_DEVICE_LOST using nvidia hardware (@adamwill:fedora.im, 17:27:43)
    1. INFO: this awaiting further investigation, we need to find a developer who can look into it (@adamwill:fedora.im, 17:32:53)
  11. TOPIC:Open floor (@adamwill:fedora.im, 17:33:05)


Meeting ended at 17:34:55 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (204)
  2. @ngompa:fedora.im (65)
  3. @supakeen:fedora.im (35)
  4. @nielsenb:fedora.im (33)
  5. @kparal:matrix.org (32)
  6. @lruzicka:fedora.im (23)
  7. @derekenz:fedora.im (18)
  8. @zodbot:fedora.im (15)
  9. @kashyapc:fedora.im (15)
  10. @sgallagh:fedora.im (12)
  11. @jgroman:fedora.im (9)
  12. @osama-albahrani:matrix.org (8)
  13. @psklenar:fedora.im (3)
  14. @meetbot:fedora.im (2)
  15. @nhanlon:beeper.com (1)
  16. @conan_kudo:matrix.org (1)
  17. @decathorpe:fedora.im (1)


1 Like