Created attachment 701049 [details] bug demonstration video Description of problem: I tried to shrink the Windows partition to free space for Fedora. Problem 1: The dialog said Fedora needs 3.47 GB, I freed 4.5 GB, but I was then told I still don't have enough space. That is bug 876916 - the installer doesn't account for non-root partitions, like swap. Problem 2: The shrinking dialog allows me to shrink only if the amount of space freed is larger than the amount of space required. That's reasonable. But if I run the dialog a second time, it doesn't remember I already freed space. Therefore I'm again forced to free >= 3.47GB, I can't free just an additional 1 GB, for example. See video. Version-Release number of selected component (if applicable): anaconda 19.8 How reproducible: always Steps to Reproduce: 1. create a 10 GB disk and a single 10 GB NTFS partition 2. follow video
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Is this still reproducible with F20 images?
This particular bug is resolved with F20 Beta TC4. However, during resize operation there is no progress indicator displayed, no message, no nothing, and anaconda looks like frozen. I almost killed it, because I had no idea that something was happening in the background.
(In reply to Kamil Páral from comment #3) > This particular bug is resolved with F20 Beta TC4. However, during resize > operation there is no progress indicator displayed, no message, no nothing, > and anaconda looks like frozen. I almost killed it, because I had no idea > that something was happening in the background. The resize operation runs on the Progress hub and the spinner is spinning at that time. Where did you experience the hang? When leaving the reclaim dialog? Could you please test it once more (it maight be a coincidence of bad timing with some yum_lock-based hang) and file a separate bug if it happens regularly?
(In reply to Vratislav Podzimek from comment #4) > The resize operation runs on the Progress hub and the spinner is spinning at > that time. Where did you experience the hang? When leaving the reclaim > dialog? Could you please test it once more (it maight be a coincidence of > bad timing with some yum_lock-based hang) and file a separate bug if it > happens regularly? Oh, ok, the resize happens only after the installation is started. I got confused. The "freeze" happens after return to the main hub. Reported as bug 1020373.