2026-08-31 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

Hi folks! It’s time for a Fedora 45 blocker (and FE) review meeting! We have 1 proposed blocker and 3 proposed freeze exception for Beta, and 1 proposed blocker 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 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. This page 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 F45 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!

2 Likes

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:01:12)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:03:57)
    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:03:57)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:03:57)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:03:57)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:03:57)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:03:57)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:03:57)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:03:57)
    8. LINK: https://fedoraproject.org/wiki/Fedora_45_Beta_Release_Criteria (@adamwill:fedora.im, 16:03:57)
    9. LINK: https://fedoraproject.org/wiki/Fedora_45_Final_Release_Criteria (@adamwill:fedora.im, 16:03:57)
    10. INFO: for Beta, we have: (@adamwill:fedora.im, 16:04:27)
    11. INFO: 1 Proposed Blockers (@adamwill:fedora.im, 16:04:32)
    12. INFO: 3 Accepted Blockers (@adamwill:fedora.im, 16:04:32)
    13. INFO: 3 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:04:38)
    14. INFO: 7 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:04:38)
    15. INFO: for Final, we have: (@adamwill:fedora.im, 16:04:50)
    16. INFO: 1 Proposed Blockers (@adamwill:fedora.im, 16:04:54)
    17. INFO: 2 Accepted Blockers (@adamwill:fedora.im, 16:04:54)
    18. INFO: adamw will secretarialize (@adamwill:fedora.im, 16:07:25)
  3. TOPIC:Proposed Beta blocker (@adamwill:fedora.im, 16:07:36)
    1. INFO: correction: Lukáš Růžička will secretarialize (@adamwill:fedora.im, 16:07:48)
  4. TOPIC:(2524940) Black screen instead of the login screen after plasma-login-manager crashed in PlasmaQuick::QuickViewSharedEngine (@adamwill:fedora.im, 16:07:55)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2524940 (@adamwill:fedora.im, 16:07:55)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2153 (@adamwill:fedora.im, 16:07:55)
    3. INFO: Proposed Blocker, plasma-login-manager, NEW (@adamwill:fedora.im, 16:07:55)
    4. INFO: Ticket vote: BetaBlocker (+6,0,-0) (+geraldosimiao, +niknikovsky, +derekenz, +korora, +aggraxis, +nielsenb) (@adamwill:fedora.im, 16:07:55)
    5. AGREED: 2524940 - punt (delay decision) - though this has a lot of ticket votes, the situation seems unclear. Neal and Derek can't reproduce it. openQA only hit it briefly then stopped hitting it after I forced a buildroot regeneration. It's not happening on openQA compose tests either. Two other folks besides Steve claim to have hit it, but it's not clear that the cases are the same. We will ask the reporters to provide more logs and compare notes on package sets (@adamwill:fedora.im, 16:21:01)
  5. TOPIC:Proposed Beta freeze exceptions (@adamwill:fedora.im, 16:21:28)
  6. TOPIC:(2526278) run-gui-backend: wrong DRM card selection and broken exit code on systems with multiple GPUs (RPi4) (@adamwill:fedora.im, 16:21:46)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2526278 (@adamwill:fedora.im, 16:21:46)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2155 (@adamwill:fedora.im, 16:21:46)
    3. INFO: Proposed Freeze Exceptions, initial-setup, POST (@adamwill:fedora.im, 16:21:46)
    4. AGREED: 2526278 - AcceptedFreezeException (Beta) - this is accepted as it can make weston-based, graphical initial-setup unusable on Raspberry Pi. It's not obviously a blocker because we can't find a clear path where a release-blocking image would typically require graphical weston-based initial-setup to work (@adamwill:fedora.im, 16:29:14)
  7. TOPIC:(2524952) kmscon: NULL pointer dereference in seat_monitor_hotplug_dev when DRM device fails to initialize (@adamwill:fedora.im, 16:29:27)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2524952 (@adamwill:fedora.im, 16:29:27)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2156 (@adamwill:fedora.im, 16:29:27)
    3. INFO: Proposed Freeze Exceptions, kmscon, NEW (@adamwill:fedora.im, 16:29:27)
    4. AGREED: 2524952 - AcceptedBlocker (Beta) - this is accepted as a blocker (not FE) because it can easily cause text mode initial setup to crash before a user account can be created, rendering the system inaccessible. Text mode initial setup is used in the release-blocking aarch64 minimal disk image (@adamwill:fedora.im, 16:36:59)
  8. TOPIC:(2524726) Update to pcmanfm-qt, fixes a bunch of small bugs (@adamwill:fedora.im, 16:37:13)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2524726 (@adamwill:fedora.im, 16:37:13)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2151 (@adamwill:fedora.im, 16:37:13)
    3. INFO: Proposed Freeze Exceptions, pcmanfm-qt, ON_QA (@adamwill:fedora.im, 16:37:13)
    4. INFO: Ticket vote: BetaFreezeException (+0,0,-2) (-geraldosimiao, -nielsenb) (@adamwill:fedora.im, 16:37:13)
    5. AGREED: 2524726 - RejectedFreezeException (Beta) - there's no clear justification for this to break the freeze, it appears it could be fine as a 0-day fix for Beta, and will still make Final (@adamwill:fedora.im, 16:41:44)
    6. INFO: a new proposed Beta blocker appeared, so we'll go back to: (@adamwill:fedora.im, 16:41:52)
  9. TOPIC:Proposed Beta blocker (redux) (@adamwill:fedora.im, 16:41:58)
  10. TOPIC:(2526398) Anaconda does not report to Bugzilla after simulated crash (@adamwill:fedora.im, 16:42:05)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2526398 (@adamwill:fedora.im, 16:42:05)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2157 (@adamwill:fedora.im, 16:42:05)
    3. INFO: Proposed Blocker, anaconda, NEW (@adamwill:fedora.im, 16:42:05)
    4. AGREED: 2526398 - AcceptedBlocker (Beta) - this is accepted as a clear violation of Basic criterion "The installer must be able to report failures to Bugzilla, with appropriate information included" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Failure_reporting (@adamwill:fedora.im, 16:45:51)
  11. TOPIC:Proposed Final blocker (@adamwill:fedora.im, 16:46:29)
  12. TOPIC:(2502678) DiscoverNotifier does not show update notifications in system tray although Discover detects updates (@adamwill:fedora.im, 16:46:45)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2502678 (@adamwill:fedora.im, 16:46:45)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2148 (@adamwill:fedora.im, 16:46:45)
    3. INFO: Proposed Blocker, plasma-discover, NEW (@adamwill:fedora.im, 16:46:45)
    4. AGREED: we will close this as NOTABUG for now as Derek thinks the behavior is likely intended (@adamwill:fedora.im, 16:49:03)
  13. TOPIC:Accepted Beta blocker review (@adamwill:fedora.im, 16:50:11)
  14. TOPIC:(2490607) httpd gets stuck during FreeIPA replica enrolment with OpenSSL 4 (@adamwill:fedora.im, 16:50:20)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2490607 (@adamwill:fedora.im, 16:50:20)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2137 (@adamwill:fedora.im, 16:50:20)
    3. INFO: Accepted Blocker, httpd, NEW (@adamwill:fedora.im, 16:50:20)
    4. INFO: this does seem to be moving along, there is movement on https://github.com/dogtagpki/jss/pull/1116 . developers told me they do expect/hope something to be ready in time for the go/no-go cutoff (@adamwill:fedora.im, 16:51:04)
  15. TOPIC:(2483236) QtWebView browser applications (like slitherer) cannot properly open native HTML dropdowns (@adamwill:fedora.im, 16:53:46)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2483236 (@adamwill:fedora.im, 16:53:46)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2136 (@adamwill:fedora.im, 16:53:46)
    3. INFO: Accepted Blocker, qt6-qtwebengine, NEW (@adamwill:fedora.im, 16:53:46)
    4. INFO: this is still waiting on upstream, but we do have the option of forcing slitherer to use xcb as a possible workaround if no real fix appears in time (@adamwill:fedora.im, 16:57:41)
  16. TOPIC:(2484542) kmscon implementation breaks console initial-setup (@adamwill:fedora.im, 16:59:48)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2484542 (@adamwill:fedora.im, 16:59:48)
    2. LINK: https://forge.fedoraproject.org/quality/blocker-review/issues/2139 (@adamwill:fedora.im, 16:59:48)
    3. INFO: Accepted Blocker, selinux-policy, NEW (@adamwill:fedora.im, 16:59:48)
    4. INFO: we are waiting on feedback from the selinux maintainer here, we will needinfo him (@adamwill:fedora.im, 17:02:21)
  17. TOPIC:Open floor (@adamwill:fedora.im, 17:03:18)


Meeting ended at 17:07:46 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (144)
  2. @conan_kudo:matrix.org (40)
  3. @supakeen:fedora.im (26)
  4. @goroboro:matrix.org (18)
  5. @derekenz:fedora.im (16)
  6. @lruzicka:fedora.im (15)
  7. @ephmo:fedora.im (13)
  8. @nielsenb:fedora.im (12)
  9. @geraldosimiao:matrix.org (12)
  10. @korora:fedora.im (11)
  11. @zodbot:fedora.im (11)
  12. @niknikovsky:fedora.im (8)
  13. @jgroman:fedora.im (5)
  14. @kparal:matrix.org (4)
  15. @meetbot:fedora.im (2)
  16. @farchord:fedora.im (1)