Description of problem: I've been reviewing the usability test video from Brno. In Video 3/ User 2 / 1361621939636667, the user attempts to install Fedora dual-boot with a pre-existing Windows installation (on a VM). The disk is 10 GB large. The Windows install takes up roughly 9 GB. The user did not do custom partitioning; they selected the 10 GB disk and when exiting the disk selection screen were informed there wasn't enough free space on disk and they'd need to reclaim at least 3.47 GB of space to install Fedora. The user used the reclaim space dialog and freed 5 GB of space from the Windows 9 GB partition, shrinking Windows down to 4 GB. When the user exited the reclaim space dialog, they were told they still didn't have enough space. The dialog specifically said they needed 3.47 GB to install Fedora and had 5.09 GB of space free. This doesn't make sense and the user was quite confused as what to do. I talked to dlehman about this in IRC and he said he thinks that the system probably would require > 1.5GB of swap that isn't accounted for in the 3.47 GB number. So the UI figure of '#.47 GB' is not reflecting the installer's actual space requirement, which is higher. So the bug here is that the number that the 'not enough space' dialog presents to the user does not include the amount of space they need for swap, depending on their system's memory. It should so users know how much space to free up to successfully finish the install. Version-Release number of selected component (if applicable): It was Fedora 18 GA on a VM in Brno, but the bug is still present in F19.
Here's a suggested language change for the text to account for this addition of required space: X = amount of space required to install fedora Y = amount of space required for swap Z = X + Y "Your current software selection requires Z amount of available space, including X for software and Y for recommended swap."
*** Bug 952512 has been marked as a duplicate of this bug. ***
anaconda-19.22-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.22-1.fc19
Package anaconda-19.22-1.fc19, pykickstart-1.99.28-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.22-1.fc19 pykickstart-1.99.28-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6595/pykickstart-1.99.28-1.fc19,anaconda-19.22-1.fc19 then log in and leave karma (feedback).
*** Bug 957368 has been marked as a duplicate of this bug. ***
anaconda-19.22-1.fc19, pykickstart-1.99.28-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 876091 has been marked as a duplicate of this bug. ***