Description of problem: When installing from the live CD, Anaconda reports that an unhandled exception has occured, apparently while it's searching for disk drives. This happens immediately after selecting the keyboard type and clicking the Next button. You are given the opportunity to save a copy of the exception or exit the installer. If you save a copy, the installer will exit after the copy has been saved. Version-Release number of selected component (if applicable): How reproducible: Very easily reproduced. Steps to Reproduce: 1.Boot from LiveCD 2.Double-click on the "Install to Harddrive" desktop icon 3.Click "Next" on initial installer screen 4.Select your keyboard type 5.Click "Next" Actual results: Unhandled error occurs Expected results: Screen displaying disks/partitions is displayed enabling user to select installation location. Additional info: As you'll probably gather from the InstallError.txt, I have 5 disks with multiple partitions. The disk that may be the problem is sde, which already has a Ubuntu installation on 2 of the partitions ("/" on sde4 and "/home" on sde1). I did run the fedora installer previously without the unhandled exception occuring but parted refused to install onto the partition I wanted (something to do with the partition being ext4) so I used gparted to repartition the disk so the target partition was ext3 and was a primary partition (it was a logical drive before which I thought could be causing an issue). Sorry guys, I've used plenty of linux distros and this has been the most temperamental installer I've had the displeasure to use. Despite the strong desire to use Fedora 11, this issue has completely blocked me from actually getting it installed. Please advise.
Created attachment 347330 [details] This is the error report that the installer saved.
Your bug appears to be a known problem in parted, and perhaps nothing to do with anaconda though we won't know that until after we get parted fixed up. Thanks for the snark - we weren't getting enough of it already. *** This bug has been marked as a duplicate of bug 501768 ***