Created attachment 734463 [details] anaconda traceback When running liveinst from the Fedora 19 Alpha TC2 KDE Live, I get a traceback immediately upon entering Custom Partitioning and expanding the other OS partitions lists. (This machine currently has the default partition layout for a brand new Dell laptop, e.g. ESP + NTFS + FAT32 recoverycrap.)
Created attachment 734464 [details] anaconda.log
Created attachment 734465 [details] ifcfg.log
Created attachment 734466 [details] program.log
Created attachment 734467 [details] storage.log
Actually, this occurs when I click on the primary NTFS partition of the preinstalled Windows installation. I had to blow away this partition with parted to get around it and proceed with installation.
Sorry, I meant F19 Alpha RC2.
Proposing as a Fedora 19 Beta Blocker because it violates criterion 10: "The installer's custom partitioning mode must be capable of the following: Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types". Also proposing as an F19 Alpha Freeze Exception because it's similar to bug 950700 in that it's a custom partitioning issue but one somewhat likely to be hit, assuming it affects all systems with Windows 8 preinstalled.
Discussed at 2013-04-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-15/f19alpha-blocker-review-7.2013-04-15-16.00.log.txt . Rejected as an FE issue: it's quite late at this point and we want to be safe, this patch is as-yet untested and touches partitioning code, so could _theoretically_ break something worse.
python-blivet-0.11-1.fc19,anaconda-19.19-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.11-1.fc19,anaconda-19.19-1.fc19
Package python-blivet-0.11-1.fc19, anaconda-19.19-1.fc19, lorax-19.2-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 python-blivet-0.11-1.fc19 anaconda-19.19-1.fc19 lorax-19.2-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5795/lorax-19.2-1.fc19,python-blivet-0.11-1.fc19,anaconda-19.19-1.fc19 then log in and leave karma (feedback).
Package python-blivet-0.11-1.fc19, lorax-19.2-1.fc19, anaconda-19.20-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 python-blivet-0.11-1.fc19 lorax-19.2-1.fc19 anaconda-19.20-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5795/lorax-19.2-1.fc19,python-blivet-0.11-1.fc19,anaconda-19.20-1.fc19 then log in and leave karma (feedback).
python-blivet-0.11-1.fc19, lorax-19.2-1.fc19, anaconda-19.20-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.