Created attachment 749240 [details] textmode-lvm.txt Description of problem: In text mode, before root password is set, both "create user" and "set root password" have [!]. Once "set root password" is set, both have [x], but "create user" has not jet been configured. Version-Release number of selected component (if applicable): Fedora 19 Beta RC2 anaconda-19.28-1.fc19 How reproducible: always Steps to Reproduce: 1. Start text mode installation 2. don't create user but set root password 3. continue with installation Actual results: Installation 1) [x] Timezone settings 2) [x] Install Destination (Europe/Luxembourg timezone) (Automatic partitioning selecte 3) [x] Create user d) (No user will be created) 4) [x] Set root password (Password is set.) Please make your choice from above ['q' to quit | 'c' to continue]: Expected results: Installation 1) [x] Timezone settings 2) [x] Install Destination (Europe/Luxembourg timezone) (Automatic partitioning selecte 3) [ ] Create user d) (No user will be created) 4) [x] Set root password (Password is set.) Please make your choice from above ['q' to quit | 'c' to continue]: Additional info: Attaching full installation progress.
Created attachment 749242 [details] anaconda.ifcfg.log
Created attachment 749243 [details] anaconda.log
Created attachment 749244 [details] anaconda.packaging.log
Created attachment 749245 [details] anaconda.program.log
Created attachment 749246 [details] anaconda.storage.log
Created attachment 749248 [details] syslog
This indicates that the spoke doesn't need to be visited. Note that it does say "(No user will be created)" below it. I'm not sure if we want to change this or not.
(In reply to Brian C. Lane from comment #7) > This indicates that the spoke doesn't need to be visited. Note that it does > say "(No user will be created)" below it. I'm not sure if we want to change > this or not. We probably should, yes.
I take back my previous comment. Text behavior mirrors what is seen in graphical install. I see no reason to change that and break consistency. As far as I am concerned this is not a bug.