Created attachment 562499 [details] Crash report file Description of problem: I tried installing Fedora 17 TC2 (this also happened on RC2) on my system. I selected custom partitioning scheme and deleted an LVM logical volume named lvfedora15 to create a new logical volume with a new name (e.g. lvfedora17). Anaconda crashes on creating a new LVM logical volume Version-Release number of selected component (if applicable): Anaconda in both Fedora 17 TC2 and RC2 How reproducible: 100% Steps to Reproduce: 1. Run Fedora 17 installer up to the partitioning screen 2. Delete lvfedora15 logical volume 3. Press Create and select LVM logical volume Actual results: Anaconda crashes Expected results: Anaconda should bring an screen to enter the logical volume properties (e.g. name and size).
Created attachment 562500 [details] Another crash report file: this time from the main partitioning screen (the other one was inside LVM partition editor)
Please attach /tmp/anaconda-tb-* as an uncompressed attachment. Doing anything else results in us being unable to search bugzilla later (like, if we need to find duplicates).
And please be sure to attach logs from RC2 since it is the latest.
Created attachment 564087 [details] Crash report (RC2)
anaconda-17.10-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.10-1.fc17
anaconda-17.11-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.11-1.fc17
Package anaconda-17.11-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.11-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2185/anaconda-17.11-1.fc17 then log in and leave karma (feedback).
anaconda-17.11-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.