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 F43 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.
Here is an AI-generated summary of a Blocker review meeting from 2025-10-20.
Please be aware that the summary is intended for a quick convenient recapitulation of the meeting, but might contain factual errors. Read the full meeting log for all the details.
Problem: The Anaconda WebUI installer encounters an error when the live system uses the ‘typing-booster’ layout, preventing installation.
Resolution: Rejected as a Final Blocker, Accepted as a Final Freeze Exception. After analysis, the group concluded that the Workstation experience is no worse than in F42, and the KDE experience is “manageably awkward”. It was accepted as a Freeze Exception to allow for improved error messages or well-tested improvements if the release schedule slips.
Problem: The postfix.service is disabled after a system upgrade.
Resolution: Rejected as a Final Blocker, Accepted as a Final Freeze Exception. The issue is not believed to technically violate the release criteria and is not specific to Fedora 43. It is suspected to be an interaction between a chkconfig change (present in both F42 and F43) and systems that were previously upgraded to F42 using specific, individual symlinks rather than the main /usr/sbin → /usr/bin symlink. It was accepted as a Freeze Exception to allow a fix to land during the freeze period if one is found.
Problem:gnome-session-service crashes during the initial installation process due to a systemd timeout.
Resolution: Punted (decision delayed). The meeting did not reach a clear consensus, with the vote at +2 / -4. A separate bug was filed for an issue seen on Peter Robinson’s Pinebook Pro, and the team is awaiting further details.
Problem: The firmware device tree fallback mechanism is not functioning correctly.
Resolution: Accepted as a Final Blocker. The bug is believed to affect common configurations of the Raspberry Pi 4, a very popular device for Fedora aarch64, as well as the Nanopi R5C.
Problem: The 7zip application fails to find a required library when executed using its full path.
Resolution: Accepted as a Final Blocker. This issue was upgraded from a proposed Freeze Exception. It is considered a blocker because it violates the criterion requiring archive managers to function, as testing showed it breaks all standard archive interactions in KDE (Ark, Dolphin).
Resolution: Accepted as a Final Freeze Exception. This was accepted to address a vulnerability as soon as possible and to avoid needing a version bump immediately after release.
Problem: The slitherer installer process causes very high CPU usage on systems without 3D acceleration, such as in VMs or on bare metal with nomodeset.
Resolution: Accepted as a Final Freeze Exception. This was accepted because it impacts the usability of the live installer in unaccelerated environments and cannot be fixed with a standard post-release update.
Problem: The dracut default “sloppy” hostonly mode leads to a significant increase in the size of the initramfs.
Status: The intended fix has been pushed to stable, but the team is still waiting for someone to test and provide data on the new image sizes, comparing them ideally to dracut 105.