Check Fedora 45’s Remaining Startup Reports Before Installing

A Workstation live USB that opens a login screen instead of its desktop is still represented in Fedora 45’s release tracker. So is a separate Windows BitLocker boot problem. Neither appeared in the accepted-blocker section when we checked on October 30. Here is how to find the reports relevant to an installation without confusing their release classifications.

Find the report for your startup path

Use the Fedora BlockerBugs list before choosing an image to test. The page groups reports by their treatment in the release process; reading only its empty blocker section would miss both entries.

1. Confirm that the selected milestone is F45 Final. The navigation also offers F45 Beta, which is a different checkpoint.
2. Under Accepted Freeze Exception, find GDM bug 2501223. Its summary describes Workstation live images sometimes starting GDM instead of the desktop, with a desktop on tty2 showing an authentication prompt.
3. If the computer also boots Windows with BitLocker, look under Prioritized Bug for grub2 report 2049849. That entry concerns chainloading Windows; its summary identifies bootnext as the needed route.
4. Read the status column as well as the section heading. Both entries were NEW in the snapshot whose sync time was October 30 at 19:00 UTC.

The GDM report points to a useful test on your intended hardware: does that particular live image reach its desktop normally? Note the image build when recording the result. Successful startup tells you about that path on that computer, rather than completing every compatibility check for the installation.

Use the classification to choose the next check

An accepted freeze exception is permission to include a qualifying fix during the freeze. It does not say a fix is already installed in the image you downloaded. Fedora’s exception procedure explains why these reports receive attention without necessarily preventing a milestone release.

On a dual-boot machine, inspect the Windows boot arrangement before changing Linux. The grub2 summary describes a boot-selection problem, not damaged Windows files. Keep the existing recovery route understood and available. Disabling BitLocker is not a remedy established by this tracker entry.

There were no proposed or accepted blockers in the checked list. The release schedule nevertheless remains a separate reference, with November 3 listed as the current final target. Use the final announcement to establish release availability; use individual reports to decide what needs exercising locally.

Console-dependent workflows deserve their own test after boot. Our kmscon migration guide covers terminal paths and graphics launchers. Keep those findings alongside the live-image build and dual-boot notes, so an eventual upgrade decision reflects the computer’s actual jobs.