Created attachment 690356 [details] bug demonstration video Description of problem: When trying to verify bug 824416 I was confronted with _so many bugs_, that I refuse to create separate reports for them. I feel really burned out when it comes to Anaconda partitioning. I just dump here the whole video and you can split it or deal with it however you want. Intention: Install Fedora while re-using existing /home and enlarging it at the same time. Timings and issues in the video: 1:05 - If you mount partition first and then try to enlarge it, it is not enlarged. Reformatting doesn't help (I didn't want to reformat it, but I wanted to test whether it would help me enlarge the partition). 1:29 - If I set a partition to be reformatted, I can't take it back. The checkbox is very devious, it seems to be unset unless you select the partition again, then you see it set again. That means some folks will reformat their partitions without knowing. This is the reason why every other installer shows a summary screen "following changes will be performed" before actually touching the disk. But Anaconda doesn't understand that user data are precious. 2:12 - The bottom bar says "Please enter a valid mountpoint" without an obvious reason. /home is a valid mountpoint. 2:22 - Size specification of "500M" is translated to 7238 MB. 2:43 - The screen is shrunk for no apparent reason. 3:11 - Adding 1 MB biosboot partition while having 1.96 MB free resulted in: a) error "not enough space" b) removing / partition without a reason Also throughout the video you might see that sometimes when I return back to partitioning screen the disk layout is reset to the original layout, but sometimes my previous actions are kept and I can continue. There is no wonder people prefer to reboot the installation media when they make a mistake in partitioning, it just seems safer. Version-Release number of selected component (if applicable): Fedora 18 How reproducible: 100% Steps to Reproduce: 1. just follow the video
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.