Description of problem: see the summary and maybe bug 439967 Version-Release number of selected component (if applicable): dracut-018-98.git20120813.fc17.noarch How reproducible: boot the box with USB peripherals connected Actual results: USB messages past the password prompt, when user starts typing nothing is printed or re-printed. We're typing in a black hole as if it were. Expected results: password prompt re-printed as it was before a soon as the user starts typing, asterisks printed maybe for password characters Additional info:
Do you have plymouth installed? dracut cannot do anything about kernel messages getting printed. Either start the kernel with "quiet" on the kernel command line or use plymouth.
No plymouth. The behaviour of the password prompt has changed: in the old situation the prompt was overwritten but *re-printed* as soon as one started typing the password. In the current situation it is *not* re-printed.
Without plymouth, and with systemd in the initramfs, dracut uses the systemd mechanism. Without systemd, dracut uses cryptsetup itsself. Reassigning to systemd.
Are we sure we don't have systemd in initramfs? In dmesg I see: dracut: luksOpen /dev/md1 crypto none
Can I help here?
Let me get this right: you are not using plymouth, but you get a password prompt, that scrolls away. When you type something you don't see feedback, but the passphrase is accepted?
Indeed.
Have did you turn off plymouth? Did you uninstall it? If so, did you rebuild the initrd? Did you use plymouth.enable=0? Did you drop rhgb from the cmdline?
I did uninstall plymouth. I did build multiple kernels since that moment. I did not use plymouth.enable=0.. I did remove rhgb earlier than that: title Fedora (3.6.11) root (hd0,0) kernel /vmlinuz-3.6.11 ro root=/dev/myvg/rootlv noexec=on noexec32=on vga=0x0F01 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us acpi_enforce_resources=lax fbcon=font:VGA8x16 radeon.pcie_gen2=1 cgroup_disable=memory threadirqs initrd /initramfs-3.6.11.img
hmm, normally we should refrehs the prompt on every keypress. something is fishy. does TAB have any effect?
I did not try TAB but will do so on next reboot.
Rebooted, TAB did not do anything. Also I noticed that systemd still tries to start plymouth, even while it was deinstalled completely.
(In reply to comment #12) > Rebooted, TAB did not do anything. > Also I noticed that systemd still tries to start plymouth, even while it was > deinstalled completely. What is the output of: # lsinitrd | fgrep systemd ??
# lsinitrd | fgrep systemd drwxr-xr-x 2 root root 0 May 20 08:04 usr/lib/systemd -rwxr-xr-x 1 root root 21160 Feb 15 10:33 usr/lib/systemd/systemd-timestamp lrwxrwxrwx 1 root root 27 May 20 08:04 usr/lib64/libsystemd-journal.so.0 -> libsystemd-journal.so.0.0.3 lrwxrwxrwx 1 root root 26 May 20 08:04 usr/lib64/libsystemd-daemon.so.0 -> libsystemd-daemon.so.0.0.1 lrwxrwxrwx 1 root root 25 May 20 08:04 usr/lib64/libsystemd-id128.so.0 -> libsystemd-id128.so.0.0.3 -rwxr-xr-x 1 root root 17040 Feb 15 10:33 usr/lib64/libsystemd-daemon.so.0.0.1 -rwxr-xr-x 1 root root 75264 Feb 15 10:33 usr/lib64/libsystemd-journal.so.0.0.3 -rwxr-xr-x 1 root root 25576 Feb 15 10:33 usr/lib64/libsystemd-id128.so.0.0.3
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Loads of bugzilla emails won't help.
Please just reprint the password prompt at the first keypress.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.