Created attachment 710835 [details] Disk space problem where Graphical installer is stuck Description of problem: I wanted to install latest Fedora 19 live (night build 20130310.17) in virtual machine over existing F18 installation (system re-installation). F18 uses 5 GB of total 8 GB virtual disk. Graphical installer complains there is insufficient disk space available for installation (3 GB). There is no possibility / option to choose / use disk with existing system for its re-installation. I have no other way then to cancel the installation at this point. Installer does not offer any other option on this screen (see attached screenshot). Because of virtual machine, I can delete existing v-drive and create new empty one. If I would need to install this OS on physical machine, I would need to format drive through live CD first and then install the new system on empty drive. This solution should be offered and performed with installer directly. Version-Release number of selected component (if applicable): Fedora-19-Nightly-20130310.17-x86_64-Live-desktop.iso How reproducible: Always Steps to Reproduce: 1. Start live CD of above mentioned image over existing system (lets have the available drive free space less then minimum needed for OS installation). 2. Confirm to install live system to disk. 3. Installer is stuck on second or third (don't remember now) screen. It provides message with disk space problem and offers just and only quit button. Actual results: Graphical installer is stuck when the target drive does not offer enough disk space for OS installation. Expected results: Give me overview of existing drives in my machine and let me choose the desired location for new system installation. Or let the installer offer several possibilities like use free space for installation, use space being occupied with existing OS, etc. (like possibilities that were offered with old anaconda installer).
I don't understand why people keep reporting this as a disk space problem instead of the obvious problem: There aren't any spokes available on the hub. Anyway, this is a problem with something in libxklavier changing format, and a newer anaconda build contains the fix.