Fedora 45 is delayed again. At the Go/No-Go meeting on 22 October 2026, the Fedora project declared a second NO-GO for the release. Fedora 45 will not ship next week, and the new planned release date is 3 November 2026. Here is why the release keeps slipping, which bugs are blocking it, and what Fedora users should do while they wait.
Why Fedora 45 Missed the Date Again
The trouble started earlier. Fedora 45 was not released this week as its ideal early release target because the project did not have a release candidate build in time for the previous week’s Go/No-Go meeting. At this week’s meeting, the release slipped by at least one more week due to open blocker bugs.
The Go/No-Go meeting is Fedora’s release gate. Release engineering, QA and working group members review the blocker list together and vote. If accepted blockers remain open, the vote is NO-GO and the release does not happen. Fedora 45 has now failed that vote twice.
For now, the planned release date is 3 November 2026. Whether that date holds depends on whether the blockers are addressed by next Thursday. Fedora does not move the calendar date until the bugs actually close, so another slip is possible. If the blockers are not resolved by the next meeting, the project will hold another vote and push the date again rather than ship a broken upgrade path.
The Bugs Blocking Fedora 45
Accepted Blockers
These are confirmed release blockers that must be fixed before Fedora 45 ships:
- An update is needed to mitigate issues with eMudhra, the certificate authority that recently dropped out of the global SSL/TLS certificate business after problems with its operations.
- The Fedora Server 45 AArch64 image exceeds its maximum allowed size.
- LVM auto-activation fails after upgrading to Fedora 45 on a LUKS-backed physical volume setup.
- KDE Plasma Discover installs outdated native RPM packages from the Fedora 44 repository instead of the Fedora 45 ones.
Proposed Blockers Under Review
- No network interface gets configured via the ip= kernel parameter during installation.
- A Stratis encrypted pool fails to boot.
- An encrypted Stratis root drops to emergency mode after an unanswered passphrase prompt.
There is also a handful of granted freeze exceptions, meaning specific fixes can land even while the release is otherwise frozen. The live blocker list is maintained at qa.fedoraproject.org for anyone who wants to track the status day by day.
What Arrives When Fedora 45 Finally Ships
The delay does not change what is inside the release. Fedora 45 was previewed in the beta with some of the most visible desktop changes in years.
- GNOME 51, the newest version of the default Fedora Workstation desktop, with the latest GNOME design language and performance work.
- KMSCON console support, replacing the old framebuffer console setup with a modern kernel-mode-setting console.
- Smoother experience for Snapdragon X laptops, following the push to make Linux work well on Arm-powered PCs.
- Under-the-hood updates across toolchains, the kernel and the usual Fedora package refresh.
The eMudhra mitigation on the blocker list is itself a sign of the times. Fedora, like every distribution, has to ship certificate store updates when a certificate authority runs into trouble, and that work has to be right before a release goes out the door.
How Fedora’s Release Gate Works
Fedora runs on a release train of roughly six months, with every release going through Alpha, Beta and Final stages. The Go/No-Go meeting is the final checkpoint before each stage is published. It is not a formality. QA engineers, release engineering and the working groups review every accepted blocker and vote in the open.
A bug becomes an accepted blocker when it meets the release criteria: it breaks a default install path, corrupts data, or fails hardware that Fedora claims to support. A proposed blocker is one someone has nominated but the meeting has not yet judged. Fedora 45 currently has accepted blockers in exactly the areas users notice first: installation, upgrades and desktop package management.
The system exists to protect users from exactly the failures on the current list. An LVM auto-activation failure on LUKS setups would leave upgraded systems unbootable, and a package manager pulling packages from the previous release is the kind of quiet inconsistency that causes support chaos for months. Two NO-GO votes in a row is frustrating, but shipping those bugs would be worse.
Fedora 45 vs Fedora 44: Should You Upgrade When It Lands
Fedora 44 keeps receiving updates and remains the safe choice for daily drivers until Fedora 45 proves itself. When 45 does arrive, the upgrade decision mostly comes down to which desktop and hardware you run.
- GNOME Workstation users get the biggest visible change with GNOME 51 and will see the interface evolve the most.
- KDE users should watch the Discover packaging fix land before upgrading, since the Plasma software centre is currently part of the blocker list.
- Server users on AArch64 should confirm the image size fix is in the final build before rolling it out.
- Anyone running Stratis or LUKS-backed LVM should read the release notes line by line. Storage stacks are where the current blockers live.
Fedora’s upgrade tooling (dnf system-upgrade) is mature and usually painless, but the first week after a release is when upgrade edge cases surface. Patience here costs nothing.
What Fedora Users Should Do Now
- Do not chase daily builds for production machines. If you need a stable system, Fedora 44 remains supported and receives updates.
- Test the beta if you can. Blocker bugs like the LUKS upgrade failure and the Discover packaging issue surface faster when more people run the beta and file reports.
- Watch the blocker list. qa.fedoraproject.org shows exactly which bugs stand between today and release day.
- Plan upgrades after release, not on release day. Even when Fedora 45 ships, waiting a week for post-release updates is the low-risk move.
- If you use Stratis or LUKS-backed LVM, read the release notes carefully before upgrading. Both storage stacks appear in the current blocker list.
For users on other distributions, the Fedora 45 cycle is worth watching anyway. GNOME 51 and KMSCON land in other distros later, and the fixes Fedora finds now benefit everyone.
FAQ
When will Fedora 45 be released?
The planned release date is 3 November 2026 after a second NO-GO at the 22 October Go/No-Go meeting. The date holds only if the accepted blockers are fixed by the following Thursday.
Why was Fedora 45 delayed?
Open blocker bugs remain, including an eMudhra mitigation update, an oversized Fedora Server AArch64 image, an LVM auto-activation failure on LUKS setups, and KDE Plasma Discover pulling outdated Fedora 44 packages.
What is new in Fedora 45?
Fedora 45 ships GNOME 51, KMSCON console support, smoother operation on Snapdragon X laptops, and the usual kernel and toolchain updates that come with each Fedora release.
Should I upgrade to Fedora 45 on release day?
Most users should wait a week after release for post-release updates. If you use Stratis encryption or LUKS-backed LVM, read the release notes first, since both stacks feature in the current blocker list.
Where can I track Fedora 45 release blockers?
The live blocker list is at qa.fedoraproject.org. The Go/No-Go meeting reviews it weekly and votes on whether the release can proceed.
