Description of problem: "give root passwd for maintenance (or type Control-D to continue)" reports "login incorrect" after every single keypress Version-Release number of selected component (if applicable): F14 How reproducible: at least the 2 times I tried Steps to Reproduce: 1. add a line like UUID=c2f240a3-4ebc-40fe-ae71-6cfbedf8f60a /h ext4 defaults 1 2 to /etc/fstab, where that UUID does not refer to a partition 2. reboot 3. Actual results: reboot fails with "unable to resolve UUID=..." dropping you to a shell; the system will reboot when you leave the shell Warning SELinux is active Disabling security enforcement security enforcement for system recovery Run setenforce 1 to reenable Give root password for maintenance (or type Control-D to continue): Now, pressing any single key provokes "login incorrect". Even ignoring all that and typing the correct password does not work. Expected results: reboot succeeds (though a warning would be fine and expected)
ini4j is not involved in the boot process ;) Did you mean to file this against another package?
Sorry. completion fail. I've changed the component to "initscripts"
By the way, the missing UUID is not at all related to the F14 installation. It was a data-only partition on another disk that I'd just removed.
This is likely an issue with input mode on the terminal; assigning to plymouth.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping