Red Hat Bugzilla – Bug 926926
Anaconda is not allowing continuation when custom partitioning is selected.
Last modified: 2014-06-18 05:06:38 EDT
Description of problem:
Select custom partitioning, Anaconda returns to hub screen, but does not allow any option to continue.
Steps to Reproduce:
1. Click on select disk button in main hub
2. Select install disk
3. Click Done
4. Click Custom Partition button
Anaconda does not present any options to continue the installation or select custom partitioning.
To be able to continue to a custom partitioning screen of some sort.
Proposing as a Beta blocker under the following criteria:
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
Creating encrypted partitions
Rejecting obviously invalid operations without crashin
Please attach a picture showing what you mean.
I do not see this in TC1 live...
John, I tried to reproduce your issue. Please confirm if it's what you see.. Thanks.
Reproduced on TC2:
1. Select all disks, click on Done (step1.png)
2. Click on Custom partitioning (step2.png)
Anaconda jumps directly to main hub (step3.png)
Created attachment 716463 [details]
Created attachment 716464 [details]
Created attachment 716465 [details]
Created attachment 716466 [details]
Created attachment 716467 [details]
Created attachment 716468 [details]
Created attachment 716469 [details]
Created attachment 716470 [details]
*** Bug 927927 has been marked as a duplicate of this bug. ***
Here's the problem:
11:55:14,397 ERR anaconda: Failed to import module in collect: cannot import name gtk_thread_wait
*** Bug 927951 has been marked as a duplicate of this bug. ***
I have same issue with anaconda when I want install Fedora-19-alpha TC2.
1. Select one disk (I have just one disk), click on Done
2. Click on Custom partitioning
And I return on step3.png
same here on netinstall, F19-TC2. Custom partitioning returns to hub.
Adding myself to cc.
Confirming that screenshots show what happened.
Reproduced on my test of F19 Alpha TC2 i386 which is installed into kvm.
tc2 doesn't have the fix for this, there wasn't a new anaconda build yet.
when tc3 (or other fixing this bug) will be available ?
not sure precisely, but not very long.
Verified on Fedora 19 TC 5.
19.14 went stable, so closing (this was OK in TC3).