2026-03-02 @ 17: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 freeze exceptions and 3 proposed blockers for Beta, and 1 proposed blocker for Final.

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 this weekend, 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 weekend and see you on Monday!

1 Like
2

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

Meeting started by @kparal:matrix.org at 17:00:25 UTC

Meeting summary

  1. TOPIC:Roll Call (@kparal:matrix.org, 17:00:32)
    1. LINK: http://qa.fedoraproject.org/blockerbugs/current (@lruzicka:fedora.im, 17:21:40)
    2. INFO: The bugs up for review today are available at: (@lruzicka:fedora.im, 17:21:40)
    3. LINK: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria (@lruzicka:fedora.im, 17:21:40)
    4. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@lruzicka:fedora.im, 17:21:40)
    5. INFO: The criteria for release blocking bugs can be found at: (@lruzicka:fedora.im, 17:21:40)
    6. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@lruzicka:fedora.im, 17:21:40)
    7. INFO: We'll be following the process outlined at: (@lruzicka:fedora.im, 17:21:40)
    8. 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. (@lruzicka:fedora.im, 17:21:40)
  2. TOPIC:Introduction (@lruzicka:fedora.im, 17:21:40)
    1. LINK: https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria (@lruzicka:fedora.im, 17:21:40)
    2. INFO: 4 Proposed Freeze Exceptions (@lruzicka:fedora.im, 17:22:48)
    3. INFO: 2 Accepted Blockers (@lruzicka:fedora.im, 17:22:48)
    4. INFO: 16 Accepted Freeze Exceptions (@lruzicka:fedora.im, 17:22:48)
    5. INFO: 0 Accepted 0-day Blockers (@lruzicka:fedora.im, 17:22:48)
    6. INFO: 3 Proposed Blockers (@lruzicka:fedora.im, 17:22:48)
    7. INFO: 0 Accepted Previous Release Blockers (@lruzicka:fedora.im, 17:22:48)
  3. TOPIC:Proposed blocker (@lruzicka:fedora.im, 17:23:11)
    1. INFO: Proposed Blocker, anaconda-webui, VERIFIED (@lruzicka:fedora.im, 17:23:29)
    2. INFO: Ticket vote: BetaFreezeException (+3,0,-0) (+adamwill, +derekenz, +kparal) (@lruzicka:fedora.im, 17:23:29)
  4. TOPIC:(2442593) Anaconda crash reporter passes incomplete information (@lruzicka:fedora.im, 17:23:29)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2055 (@lruzicka:fedora.im, 17:23:29)
    2. INFO: Ticket vote: BetaBlocker (+2,0,-0) (+kparal, +lruzicka) (@lruzicka:fedora.im, 17:23:29)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2442593 (@lruzicka:fedora.im, 17:23:29)
    4. AGREED: We believe this bug significantly impairs the problem reporting functionality in Anaconda's webUI. Therefore, we pronounce it a blocker bug. (@lruzicka:fedora.im, 17:44:02)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2048 (@lruzicka:fedora.im, 17:44:59)
    6. INFO: Ticket vote: BetaFreezeException (+3,0,-0) (+adamwill, +derekenz, +kevin) (@lruzicka:fedora.im, 17:44:59)
    7. INFO: Proposed Blocker, ibus, VERIFIED (@lruzicka:fedora.im, 17:44:59)
    8. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2439813 (@lruzicka:fedora.im, 17:44:59)
  5. TOPIC:(2439813) KDE network installs hang during scriptlets (%triggerin on ibus) (@lruzicka:fedora.im, 17:44:59)
    1. AGREED: 2439813 We reviewed this issue and agreed that, at this time and under the current criteria, it does not qualify as a release-blocking problem. Therefore, we are rejecting it as a release blocker. We are deferring further discussion and will reconsider it later as a potential Final Blocker. (@lruzicka:fedora.im, 18:03:35)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2047 (@lruzicka:fedora.im, 18:04:52)
  6. TOPIC:(2441941) Graphics break when trying to type LUKS password (@lruzicka:fedora.im, 18:04:52)
    1. INFO: Ticket vote: BetaBlocker (+2,0,-0) (+nielsenb, +psklenar) (@lruzicka:fedora.im, 18:04:52)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2441941 (@lruzicka:fedora.im, 18:04:52)
    3. INFO: Proposed Blocker, kernel, NEW (@lruzicka:fedora.im, 18:04:52)
    4. AGREED: 2441941 Given that the reported bug has so far manifested only on a specific hardware model, and we are not aware of any additional reports confirming it on other devices, we believe it does not qualify as a Beta blocker. We therefore propose to revisit and discuss it later as a potential Final blocker. (@lruzicka:fedora.im, 18:17:39)
  7. TOPIC:Proposed Freeze Exceptions (Beta) (@lruzicka:fedora.im, 18:19:25)
  8. TOPIC:(2440346) bluetoothctl broken in 5.86 (@lruzicka:fedora.im, 18:20:00)
    1. INFO: Proposed Freeze Exceptions, bluez, ON_QA (@lruzicka:fedora.im, 18:20:00)
    2. INFO: Ticket vote: BetaFreezeException (+2,0,-0) (+nielsenb, +derekenz) (@lruzicka:fedora.im, 18:20:00)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2063 (@lruzicka:fedora.im, 18:20:00)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2440346 (@lruzicka:fedora.im, 18:20:00)
    5. AGREED: 2440346 This issue significantly degrades Bluetooth functionality in bluez 5.86 by breaking standard bluetoothctl usage, affecting common workflows and multiple use cases. A fix is already available and low risk, and given the user-visible regression introduced during the freeze period, we propose accepting this as a Freeze Exception to restore expected Bluetooth behavior in the Beta release. (@lruzicka:fedora.im, 18:29:35)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2443827 (@lruzicka:fedora.im, 18:29:55)
  9. TOPIC:(2443827) libsoup3 package provides mingw directories under /usr (@lruzicka:fedora.im, 18:29:55)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2065 (@lruzicka:fedora.im, 18:29:55)
    2. INFO: Proposed Freeze Exceptions, libsoup3, MODIFIED (@lruzicka:fedora.im, 18:29:55)
    3. AGREED: 2443827 Accepted as a Freeze Exception because the current build permanently creates unintended MinGW directory trees in the main package due to incorrect %find_lang ordering. Although not functionally blocking, the issue causes persistent filesystem pollution that RPM will not automatically clean up. The fix is trivial, low risk, and already prepared, and accepting it now prevents further user impact during Beta. (@lruzicka:fedora.im, 18:34:16)
    4. INFO: Proposed Freeze Exceptions, spirv-headers, NEW (@lruzicka:fedora.im, 18:35:01)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2057 (@lruzicka:fedora.im, 18:35:01)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2442986 (@lruzicka:fedora.im, 18:35:01)
  10. TOPIC:(2442986) Freeze exception for Vulkan SDK (required by LLVM 22) (@lruzicka:fedora.im, 18:35:01)
    1. INFO: Ticket vote: BetaFreezeException (+1,0,-1) (+nielsenb, -adamwill) (@lruzicka:fedora.im, 18:35:01)
    2. AGREED: 2442986 We are not granting a Freeze Exception just for the purpose to support a potential future LLVM 22 Freeze Exception at this time, particularly since no coordinated request covering the full LLVM 22 stack has been formally presented for review and a candidate compose is already under testing. If LLVM 22 is proposed and accepted as a Freeze Exception later, the related dependencies can be considered together in a single, coherent request. (@lruzicka:fedora.im, 18:46:47)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2066 (@lruzicka:fedora.im, 18:47:34)
    4. INFO: Proposed Freeze Exceptions, xdg-desktop-portal, NEW (@lruzicka:fedora.im, 18:47:34)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2440238 (@lruzicka:fedora.im, 18:47:34)
    6. INFO: Ticket vote: BetaBlocker (+1,0,-0) (+derekenz) (@lruzicka:fedora.im, 18:47:34)
  11. TOPIC:(2440238) First start of xdg-desktop-portal sometimes times out, delaying apps start in Workstation Live by 45 seconds (@lruzicka:fedora.im, 18:47:34)
    1. AGREED: 2440238 Accepted as a Freeze Exception because this issue causes a significant, user-visible delay during first boot of the Workstation Live image, with core applications and the Welcome dialog blocked for approximately 45 seconds. Although intermittent, the regression directly impacts perceived system responsiveness and can affect automated testing. (@lruzicka:fedora.im, 18:51:21)
    2. INFO: We are leaving the Final Blockers to the ticket vote. (@lruzicka:fedora.im, 18:55:26)
    3. INFO: lruzicka will secretarialize. (@lruzicka:fedora.im, 18:59:17)
  12. TOPIC:Open Floor (@lruzicka:fedora.im, 19:01:40)


Meeting ended at 19:05:25 UTC

Action items

  1. (none)


People present (lines said)

  1. @lruzicka:fedora.im (138)
  2. @kparal:matrix.org (55)
  3. @nielsenb:fedora.im (38)
  4. @decathorpe:fedora.im (36)
  5. @derekenz:fedora.im (34)
  6. @kashyapc:fedora.im (24)
  7. @conan_kudo:matrix.org (19)
  8. @psklenar:fedora.im (18)
  9. @zodbot:fedora.im (17)
  10. @jgroman:fedora.im (7)
  11. @aggraxis:fedora.im (2)
  12. @meetbot:fedora.im (2)
  13. @azuma:pawb.social (2)
  14. @osama-albahrani:matrix.org (1)