2026-04-06 @ 16:00 UTC - Fedora 44 Blocker Review Meeting

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

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

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:51)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:06:44)
    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:06:44)
    2. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:06:44)
    3. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:06:44)
    4. LINK: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria (@adamwill:fedora.im, 16:06:44)
    5. LINK: https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria (@adamwill:fedora.im, 16:06:44)
    6. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:06:44)
    7. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:06:44)
    8. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:06:44)
    9. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:06:44)
    10. INFO: for Final, we have: (@adamwill:fedora.im, 16:06:47)
    11. INFO: 4 Proposed Blockers (@adamwill:fedora.im, 16:07:05)
    12. INFO: 5 Accepted Blockers (@adamwill:fedora.im, 16:07:05)
    13. INFO: 5 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:07:08)
    14. INFO: 3 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:07:08)
    15. INFO: adamw will secretarialize (@adamwill:fedora.im, 16:09:00)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:09:14)
  4. TOPIC:(2454156) No update notification in main Notifications view (@adamwill:fedora.im, 16:09:22)
    1. INFO: Ticket vote: FinalBlocker (+3,0,-0) (+asciiwolf, +derekenz, +nielsenb) (@adamwill:fedora.im, 16:09:22)
    2. INFO: Proposed Blocker, plasma-desktop, NEW (@adamwill:fedora.im, 16:09:22)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2091 (@adamwill:fedora.im, 16:09:22)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2454156 (@adamwill:fedora.im, 16:09:22)
    5. INFO: this has been unproposed based on manual testing which did not reproduce the bug and saw all the expected notifications (@adamwill:fedora.im, 16:14:12)
  5. TOPIC:(2448283) Selecting a non-ASCII capable keyboard layout should automatically also select US English as a second layout AND (2453216) plasma-setup Keyboard Layout page pre-selection is broken - always shows English (US) if that is the system language, otherwise shows nothing (@adamwill:fedora.im, 16:16:27)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2078 (@adamwill:fedora.im, 16:16:35)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2448283 (@adamwill:fedora.im, 16:16:35)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2453216 (@adamwill:fedora.im, 16:16:39)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2087 (@adamwill:fedora.im, 16:16:39)
    5. INFO: Proposed Blockers, plasma-setup, NEW (@adamwill:fedora.im, 16:16:46)
    6. INFO: Ticket vote 2448283: FinalBlocker (+0,0,-1) (-nielsenb) (@adamwill:fedora.im, 16:17:02)
    7. INFO: Ticket vote 2453216: FinalBlocker (+4,0,-0) (+asciiwolf, +geraldosimiao, +derekenz, +nielsenb) (@adamwill:fedora.im, 16:17:13)
    8. AGREED: 2448283 and 2453216 - AcceptedBlocker (Final) - these are accepted as blockers on the basis that we find their combined effect makes it very likely users who expect to use a "switched input" configuration will pick their layout on the Keyboard Layout page, with results that violate the criterion keyboard layout criterion and make completing the setup process impossible unless they then make another choice. We expect plasma-setup folks to consider the overall expected flow here and make improvements, then we will re-evaluate whether any blocker effects remain (@adamwill:fedora.im, 16:48:55)
    9. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2453005 (@adamwill:fedora.im, 16:49:17)
    10. INFO: Proposed Blocker, systemd, NEW (@adamwill:fedora.im, 16:49:17)
    11. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2086 (@adamwill:fedora.im, 16:49:17)
  6. TOPIC:(2453005) systemd-oomd.service is not enabled on some systems (@adamwill:fedora.im, 16:49:17)
    1. INFO: Ticket vote: FinalBlocker (+0,0,-1) (-nielsenb) (@adamwill:fedora.im, 16:49:17)
    2. AGREED: 2453005 - RejectedBlocker (Final) AcceptedFreezeException (Final) - this is rejected as it does not violate any criteria. The upgrade criterion requires that upgrade work and the upgraded system meet other criteria. The service criterion says "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present". This doesn't violate that - it's about a service not being enabled (i.e. "present"), not an enabled ("present") one failing to start. the absent service doesn't cause any significant functional issues that would violate any other criteria. It's accepted as an FE so we can put the obvious preset fix into F44 in case it helps avoid the problem in future (@adamwill:fedora.im, 17:21:24)
    3. INFO: Proposed Blocker, plasma-setup, NEW (@adamwill:fedora.im, 17:22:33)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2455469 (@adamwill:fedora.im, 17:22:33)
  7. TOPIC:(2455469) Configuring WifI network via Network pane appears to not work (@adamwill:fedora.im, 17:22:33)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2094 (@adamwill:fedora.im, 17:22:33)
    2. AGREED: 2455469 - AcceptedBlocker (Final) - this is accepted as a violation of Final criterion "If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test" on KDE (successfully setting up a wifi connection certainly seems within the realms of 'basic functionality') (@adamwill:fedora.im, 17:44:54)
    3. INFO: that's all the proposed blockers, let's move on to: (@adamwill:fedora.im, 17:45:27)
  8. TOPIC:Proposed Freeze Exceptions (@adamwill:fedora.im, 17:45:32)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2090 (@adamwill:fedora.im, 17:45:40)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2438126 (@adamwill:fedora.im, 17:45:40)
  9. TOPIC:(2438126) CVE-2026-25727 fido-device-onboard: time affected by a stack exhaustion denial of service attack [fedora-43] (@adamwill:fedora.im, 17:45:40)
    1. INFO: Proposed Freeze Exceptions, fido-device-onboard, ON_QA (@adamwill:fedora.im, 17:45:40)
    2. INFO: Ticket vote: FinalFreezeException (+2,0,-0) (+nielsenb, +derekenz) (@adamwill:fedora.im, 17:45:40)
    3. AGREED: 2438126 - AcceptedFreezeException (Final) - this involves two CVEs in a package included in IoT by default. It's not a blocker as they're Moderate not Important or higher, but still good to pull in the fixes (@adamwill:fedora.im, 17:50:36)
    4. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+nielsenb) (@adamwill:fedora.im, 17:50:46)
  10. TOPIC:(2437415) F44FailsToInstall: gala, gala-devel (@adamwill:fedora.im, 17:50:46)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2437415 (@adamwill:fedora.im, 17:50:46)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2092 (@adamwill:fedora.im, 17:50:46)
    3. INFO: Proposed Freeze Exceptions, gala, ON_QA (@adamwill:fedora.im, 17:50:46)
    4. AGREED: 2437415 - AcceptedFreezeException (Final) - this is accepted as usual for FTI fixes, it's nice to have clean release repos and it helps with upgrades during freeze (@adamwill:fedora.im, 17:56:16)
    5. INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+zbyszek, +nielsenb, +derekenz) (@adamwill:fedora.im, 17:56:25)
    6. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2093 (@adamwill:fedora.im, 17:56:25)
    7. INFO: Proposed Freeze Exceptions, rust-add-determinism, ON_QA (@adamwill:fedora.im, 17:56:25)
  11. TOPIC:(2454664) FTBFS due to rlimit bump (@adamwill:fedora.im, 17:56:25)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2454664 (@adamwill:fedora.im, 17:56:25)
    2. AGREED: 2454664 - RejectedFreezeException (Final) - there's no clear explanation why this merits an exception to the freeze. "Just in case we need it for some other reason" isn't sufficient justification; if said "other reason" emerges, that itself can be proposed as an FE and used to justify pulling this package in (@adamwill:fedora.im, 18:09:10)
    3. INFO: ok, that's all the proposals, let's quickly check in on: (@adamwill:fedora.im, 18:09:28)
  12. TOPIC:Accepted blocker review (@adamwill:fedora.im, 18:09:38)
    1. INFO: skipping ON_QA and VERIFIED bugs (@adamwill:fedora.im, 18:09:53)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2074 (@adamwill:fedora.im, 18:10:02)
    3. INFO: Accepted Blocker, mesa, NEW (@adamwill:fedora.im, 18:10:02)
  13. TOPIC:(2359799) Inital-setup: VK_ERROR_DEVICE_LOST using nvidia hardware (@adamwill:fedora.im, 18:10:02)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2359799 (@adamwill:fedora.im, 18:10:02)
    2. INFO: still waiting for more info / debugging on this, but we have at least one report from someone affected on f43 who was not affected on f44, which is good (@adamwill:fedora.im, 18:18:51)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2448365 (@adamwill:fedora.im, 18:19:00)
    4. INFO: Accepted Blocker, uboot-tools, ASSIGNED (@adamwill:fedora.im, 18:19:00)
  14. TOPIC:(2448365) rpi4 fails to boot from usb drive after upgrade to RC3 (@adamwill:fedora.im, 18:19:00)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/2079 (@adamwill:fedora.im, 18:19:00)
    2. INFO: this bug is solidly confirmed, we are waiting on peter with the fix (@adamwill:fedora.im, 18:22:14)
  15. TOPIC:Open floor (@adamwill:fedora.im, 18:22:22)


Meeting ended at 18:25:27 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (218)
  2. @ngompa:fedora.im (67)
  3. @nielsenb:fedora.im (60)
  4. @sgallagh:fedora.im (48)
  5. @derekenz:fedora.im (29)
  6. @ahmedalmeleh:matrix.org (23)
  7. @zodbot:fedora.im (9)
  8. @salimma:fedora.im (6)
  9. @mcatanzaro:gnome.org (6)
  10. @korora:fedora.im (4)
  11. @aggraxis:fedora.im (3)
  12. @nhanlon:beeper.com (3)
  13. @supakeen:fedora.im (3)
  14. @meetbot:fedora.im (2)
  15. @jlinton:fedora.im (1)