Description of problem:
When a minimal or server install option is selected, the root password is not made a mandatory option to change.
Steps to Reproduce:
1. Start anaconda
2. Select minimal install
3. Install and reboot
You are locked out of your system, since no root password was set.
You are prompted for the root password. Alternately, steps from "first boot" are run in anaconda to create an alternate user etc.
The final plan here is that the presence or absence of the firstboot package will make the root password spoke required or not. However, for now you've just got to know to go into that spoke. This is already a little bit different post-alpha in that it's moved to the progress bar hub.
*** Bug 862236 has been marked as a duplicate of this bug. ***
*** Bug 854982 has been marked as a duplicate of this bug. ***
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.15-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
With Anaconda 18.19, you have to enter the root password dialog now. You can still disable it, but then it's your conscious choice. Closing as fixed.
Kamil, you're right that is your conscious choice. However anaconda should at least warn user (if not disallow it in specific cases) that having root password disabled might result in unbootable system which is exactly the case of Minimal install and disabled root password.
Sorry, not unbootable - but unusable.
(In reply to comment #11)
Warning in certain cases would be nice, no doubt about it. But I think a separate bug would be more appropriate.
OK, filed bug 869675, closing this one.