2026-03-30 @ 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 2 proposed blockers and 2 proposed freeze exception 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 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:00:51 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:54)
    1. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:37)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:05:37)
    1. 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:05:37)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:05:37)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:05:37)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:05:37)
    5. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:37)
    6. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:37)
    7. LINK: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:37)
    8. LINK: https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria (@adamwill:fedora.im, 16:05:37)
    9. INFO: for Final, we have: (@adamwill:fedora.im, 16:05:52)
    10. INFO: 3 Accepted Blockers (@adamwill:fedora.im, 16:05:52)
    11. INFO: 3 Proposed Blockers (@adamwill:fedora.im, 16:05:52)
    12. INFO: 2 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:05:57)
    13. INFO: 3 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:05:57)
    14. INFO: kparal and/or lruzicka can fight over secretary duties (@adamwill:fedora.im, 16:10:22)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:11:23)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2451701 (@adamwill:fedora.im, 16:11:32)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2082 (@adamwill:fedora.im, 16:11:32)
  4. TOPIC:(2451701) ngtcp2-crypto-gnutls-1.21.0-1.fc43.aarch64 requires ngtcp2(aarch-64) = 1.21.0-1.fc43, but none of the providers can be installed (@adamwill:fedora.im, 16:11:32)
    1. INFO: Proposed Blocker, ngtcp2, NEW, depends on other bugs (@adamwill:fedora.im, 16:11:32)
    2. AGREED: 2451701 - punt (delay decision) - in theory we'd like to clarify why Petr's testing and openQA got different results, but in practice we suspect this is now fixed anyway because the update is now stable. So we'll just ask Petr to re-test and expect the result to be "it's fine now" and the bug to be closed (@adamwill:fedora.im, 16:26:03)
    3. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+asciiwolf) (@adamwill:fedora.im, 16:27:50)
    4. INFO: Proposed Blocker, plasma-keyboard, NEW (@adamwill:fedora.im, 16:27:50)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2081 (@adamwill:fedora.im, 16:27:50)
    6. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2449945 (@adamwill:fedora.im, 16:27:50)
  5. TOPIC:(2449945) KDE editor (kwrite, kate...) corrupts text on selection (@adamwill:fedora.im, 16:27:50)
    1. AGREED: 2449945 - AcceptedBlocker (Final) - accepted as a violation of Final criterion "For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test: ... text editor" (@adamwill:fedora.im, 16:35:14)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2078 (@adamwill:fedora.im, 16:35:23)
  6. TOPIC:(2448283) Selecting a non-ASCII capable keyboard layout should automatically also select US English as a second layout (@adamwill:fedora.im, 16:35:23)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2448283 (@adamwill:fedora.im, 16:35:23)
    2. INFO: Proposed Blocker, plasma-setup, NEW (@adamwill:fedora.im, 16:35:23)
    3. AGREED: 2448283 - punt (delay decision) - further testing has indicated there are several issues here, none of which is quite as clear-cut as first thought. we will delay the decision here so we can split this into several more specific reports that each be considered on their own merits (@adamwill:fedora.im, 17:08:58)
  7. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 17:09:21)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2444726 (@adamwill:fedora.im, 17:09:29)
    2. INFO: Proposed Freeze Exceptions, firefox, NEW (@adamwill:fedora.im, 17:09:29)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2084 (@adamwill:fedora.im, 17:09:29)
  8. TOPIC:(2444726) Workstation live Installer sometimes apparently freezes near the end, logs indicate install actually completed (@adamwill:fedora.im, 17:09:29)
    1. INFO: Ticket vote: FinalFreezeException (+2,0,-0) (+derekenz, +asciiwolf) (@adamwill:fedora.im, 17:09:29)
    2. AGREED: 2444726 - AcceptedFreezeException (Final) - there seem to be various mysterious aspects to this, but we agree that if somebody somehow figures out what's going on and finds a safe fix, the issue certainly qualifies as an FE in principle (it's a very visible and apparently-critical issue that can't be fixed with an update, even if in fact the install probably went fine and will work on reboot) (@adamwill:fedora.im, 17:22:45)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2450672 (@adamwill:fedora.im, 17:22:57)
  9. TOPIC:(2450672) Black screen after installing a number of updates including dpkg + grub (@adamwill:fedora.im, 17:22:57)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2085 (@adamwill:fedora.im, 17:22:57)
    2. INFO: Proposed Freeze Exceptions, grub2, NEW (@adamwill:fedora.im, 17:22:57)
    3. AGREED: 2450672 - AcceptedFreezeException (Final) - this is accepted on the basis that it's a pretty bad experience if you have the config that triggers this, and you can potentially hit it on upgrade to F44 during freeze since updates-testing repo is not enabled by default on stable releases, and we want to avoid that happening if possible (@adamwill:fedora.im, 17:30:50)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2086 (@adamwill:fedora.im, 17:31:15)
    5. INFO: Proposed Blocker, systemd, NEW (@adamwill:fedora.im, 17:31:15)
  10. TOPIC:(2453005) systemd-oomd.service is not enabled on some systems (@adamwill:fedora.im, 17:31:15)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2453005 (@adamwill:fedora.im, 17:31:15)
    2. INFO: NOTE: this is a new proposed blocker, we are back in blocker review, sorry for not noting it clearly (@adamwill:fedora.im, 17:31:35)
    3. AGREED: 2453005 - punt (delay decision) - there seems to be a lot of uncertainty about this ATM. we will wait for more info from the reporter, and possibly some independent re-testing of clean f42 / f43 installs and upgrades, to make the determination (@adamwill:fedora.im, 17:37:03)
  11. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 17:37:14)
    1. INFO: Accepted Blocker, mesa, NEW (@adamwill:fedora.im, 17:37:21)
  12. TOPIC:(2359799) Inital-setup: VK_ERROR_DEVICE_LOST using nvidia hardware (@adamwill:fedora.im, 17:37:21)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2359799 (@adamwill:fedora.im, 17:37:21)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2074 (@adamwill:fedora.im, 17:37:21)
    3. ACTION: adamw to try and find someone who can investigate this (@adamwill:fedora.im, 17:41:37)
    4. INFO: we are still kinda stuck waiting for any kinda technical investigation here, I will try and find someone who is able to look into it (@adamwill:fedora.im, 17:42:18)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2446745 (@adamwill:fedora.im, 17:42:24)
  13. TOPIC:(2446745) gnome-initial-setup does not enable third party repos (@adamwill:fedora.im, 17:42:24)
    1. INFO: Accepted Blocker, selinux-policy, MODIFIED (@adamwill:fedora.im, 17:42:24)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2080 (@adamwill:fedora.im, 17:42:24)
    3. INFO: this got re-opened today because the SELinux fix was necessary but not sufficient, a gnome-initial-setup fix is also needed. mcatanzaro is on it (@adamwill:fedora.im, 17:42:51)
  14. TOPIC:(2391723) `shim-ia32` missing since `shim-15.8-4` (@adamwill:fedora.im, 17:44:04)
    1. INFO: Accepted Blocker, shim, ON_QA (@adamwill:fedora.im, 17:44:04)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2391723 (@adamwill:fedora.im, 17:44:04)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2075 (@adamwill:fedora.im, 17:44:04)
    4. INFO: we believe all necessary bits of this are now done, but it would be good to get confirmation from someone with real hardware (@adamwill:fedora.im, 17:45:24)
  15. TOPIC:(2448365) rpi4 fails to boot from usb drive after upgrade to RC3 (@adamwill:fedora.im, 17:46:10)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2448365 (@adamwill:fedora.im, 17:46:10)
    2. INFO: Accepted Blocker, uboot-tools, ASSIGNED (@adamwill:fedora.im, 17:46:10)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2079 (@adamwill:fedora.im, 17:46:10)
    4. INFO: we are still waiting on a fix here, and/or for Peter to clarify what "context" is needed. Simon will test the latest uboot build and see if it changes things here (@adamwill:fedora.im, 17:48:38)
  16. TOPIC:Open floor (@adamwill:fedora.im, 17:51:17)


Meeting ended at 17:54:37 UTC

Action items

  1. adamw to try and find someone who can investigate this


People present (lines said)

  1. @adamwill:fedora.im (181)
  2. @lruzicka:fedora.im (31)
  3. @supakeen:fedora.im (21)
  4. @conan_kudo:matrix.org (19)
  5. @kparal:matrix.org (16)
  6. @derekenz:fedora.im (11)
  7. @decathorpe:fedora.im (8)
  8. @zodbot:fedora.im (7)
  9. @jgroman:fedora.im (6)
  10. @jcline:fedora.im (2)
  11. @meetbot:fedora.im (2)