Bug 905711

Sorry, but we are not dealing with rants disguised as bug reports, especially not rants with cursing and ad hominem attacks and the like.  And in general, we need bugs to have a single issue in them for ease of tracking purposes.  Anything else is pretty much impossible to follow.  I'll just give you a couple general comments:

First, did you read the help text available by clicking on the help button?  It's in the small row of buttons displayed underneath the mountpoints.  That might help some of your confusion somewhat.

Second, of course the filesystem option is insensitive until you check reformat.  Picking a filesystem without reformatting doesn't make any sense.

Third, I've cleaned up some of the confusion about the buttons and what will and won't be touched post-F18, but basically if you didn't select a drive on that first storage screen, it won't be touched.

Fourth, "Set as Boot Device" defines which drive has the first stage of the bootloader written to it, which is completely separate from /boot.

And finally (and what appears to be your real problem here) - you didn't define a /boot.  That's almost certainly why you can't continue with partitioning.  anaconda displays an error bar at the bottom and tells you to click on it for the complete error message.  Did you click on it?  If so, it probably would have told you that you needed to make a /boot.

1) A separate /boot partition is not required. Defining / without defining /boot should put /boot on the same partition as /. Besides, even if that is the problem, the UI should tell me that. Only college drop-outs write "there was an error" as the error message.

2) I've never met a programmer who's goal was to frustrate their users. Anaconda accomplishes exactly that. There are a ton of posts online from other users complaining about this "improvement." Smart programmers listen to their users.

3) Choosing not to fix a bug just because you don't like how the bug was submitted is a wee bit childish, but it is your choice. Users that don't like anaconda also have a choice, which is to choose another distro. The custom partitioning is broken in both F17 and F18, so I will probably switch to another distro the next time I am ready for an upgrade. In the meantime, kudos for getting a piece of junk implemented into production software.

"Only college drop-outs write "there was an error" as the error message."

That's a good one. Tee hee hee, ha ha ha. I have one for you:

Only childish people with poor social skills think that acting like a mean bully in a bug report is going to illicit any kind of sympathy from the developers involved in feeling a twinge of motivation to listen to what you have to say and make changes on it.

There's a lot of folks who've reported bugs with the new interface who had the self-control to use polite language when reporting them. I'm pretty sure they've got a better chance of being listened to than you.

Tom: missing /boot is not likely to be the problem, no, but we cannot possibly guess what the problem is if you don't click on the error message and tell us what it says, or attach logs, or something. We are not telepathic.

At a wild guess, you may be doing a native UEFI install - in which case you need an EFI system partition - or installing to a GPT-labelled disk - in which case you need to create a BIOS boot partition.

Let's start with:

1. A screenshot of the Manual Partitioning dialog with the Unknown partitions list expanded, so we can see what the installer is presenting. When running a Live image, you can press PrintScrn to take a screenshot -- the file is saved in ~/Pictures.

2. The installer logs from /tmp, so we can see all the details.

3. The output from:
   $ lsblk -mf # So we can see what your current storage configuration is.

Tom do you ever have heard about Rivotril or some "benzo"?, take a pill and chill out! I have some complaints but I don't use that language but they're to specific and subjective, it's my appreciation (about to have the ability to choose one by one the packages I want to install) but just that I don't think it's enough to start a flame-war about some not-a-really-bug-indeed report, it does not have any sense.

Therefore it's not a stupid UI it's a different UI. I was really confuse at first, but it became really intuitive after some setps back and then some steps forward I beg to the Anaconda's team please include it for the next release of fedora.

(In reply to comment #6)
> Tom do you ever have heard about Rivotril or some "benzo"?, take a pill and
> chill out! I have some complaints but I don't use that language but they're
> to specific and subjective, it's my appreciation (about to have the ability
> to choose one by one the packages I want to install) but just that I don't
> think it's enough to start a flame-war about some not-a-really-bug-indeed
> report, it does not have any sense.
> 
> Therefore it's not a stupid UI it's a different UI. I was really confuse at
> first, but it became really intuitive after some setps back and then some
> steps forward I beg to the Anaconda's team please include it for the next
> release of fedora.

I blew it, I writed very bad; but I guess you can understand my idea/point.

(In reply to comment #0)
...
> 9) Filling up the entire screen with the UI on a 17" screen creates a ton of
> white space that adds to the confusion.
...

What is your display resolution?
Could you attach a screenshot showing the white space?
What is confusing about the white space?

I just noticed you are using the XFCE Spin (Comment 0).
Is XFCE your usual desktop environment?

(In reply to comment #0)
...
> Maybe you should hire the developer(s) of gparted. THEY know know to develop
> an intuitive partitioning UI.
...

I agree that gparted is an excellent GUI partitioning tool. Have you ever used gparted to pre-partition a storage device before installation?