Teknozip – Fedora 44’s release has been pushed back for a second time, much to the dismay of eager Linux enthusiasts. Originally slated for April 14th, then delayed to April 21st, the new target is now April 28th. The culprit? A series of persistent "blocker bugs" that the Fedora community insists on squashing before unleashing the update upon the world.
The Fedora community takes pride in the stability of its operating system. Rather than compromise user experience, they prefer to delay a release to ensure a smooth and reliable transition. This commitment to quality, while appreciated, leaves users waiting with bated breath.
So, what exactly are these blocker bugs causing all the fuss? As reported, these are critical issues identified during the pre-release phase. Community members nominate bugs, and a voting process determines whether they qualify as "blockers". If a bug makes the list, it must be resolved before the new Fedora version sees the light of day.
Also Read
Currently, four confirmed blocker bugs are holding up the release:
| Bug ID | Component | Status | Description | Target |
|---|---|---|---|---|
| 2458907 | anaconda | ON_QA | Installation failure: Storing configuration files and kickstarts error (‘NoneType’ object has no attribute ‘path’) | testing |
| 2448283 | plasma-setup | NEW | Non-ASCII keyboard layout selection should automatically include US English as a secondary layout | |
| 2453216 | plasma-setup | POST | Keyboard Layout page pre-selection broken: always shows English (US) if that’s the system language, otherwise shows nothing | |
| 2458901 | python-blivet | ON_QA | Incomplete spanned btrfs causes anaconda to fail to detect the drive and crash during rescanning | testing |
Adding to the uncertainty, four more potential blocker bugs are under consideration. These include a black screen issue affecting ThinkPad X1 Carbon Gen 13 users and reports of slow Wi-Fi connections on certain laptop models. Should any of these be confirmed, further delays could be on the horizon.
The community can only wait and hope that the Fedora team can resolve these issues swiftly. A third delay would undoubtedly test the patience of even the most loyal Fedora users.