Reinstall Fedora scenario (with automatic partitioning) says there isn't enough space available. Reproducible: Always Steps to Reproduce: 1. Install Fedora 41 Workstation on ~40GB disk, with separate home partition / subvolume 2. Proceed through steps at https://fedoraproject.org/wiki/QA:Testcase_webui_partitioning_guided_preserve_home 3. Actual Results: The installer refuses to continue citing insufficient disk space. Expected Results: The expected partition layout should be created on the target device(s). The install process should complete successfully and the installed system should boot as expected. The partitions and subvolumes which were assigned some mountpoints in the installer should be mounted. Any partitions or subvolumes which weren't assigned any mountpoints shouldn't be mounted. Your personal files on your /home partition must be intact. Also, the error message is awkward: "No big enough free space on disks for automatic partitioning"
Created attachment 2056722 [details] Reinstall fedora scenario with error
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.