Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1103393
Summary: | plymouth takes LUKS password only from VT, not serial console | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Laszlo Ersek <lersek> | ||||
Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 23 | CC: | bill-bugzilla.redhat.com, fedora, hunter86_bg, jcm, michael.kalisz, redhatcom, rstrode, rwf, smueller | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-12-20 12:48:33 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
If I remove "console=tty" and only keep "console=ttyS0,115200n8", then plymouth takes the LUKS password from the serial console fine. However in this case I can't enter the LUKS password using the normal (USB) keyboard of course. Yes, it does work by specifying only "console=ttyS0,115200n8" but only on the serial console. However I noticed that on centos 7 that "console=tty0 console=ttyS0,115200" will let you enter the LUKS password on both consoles. Any reason why this shouldn't work the same on Fedora 20? (Sorry, my setup has changed and I can't test your suggestion, ie. "console=tty0 console=ttyS0,115200" instead of "console=tty console=ttyS0,115200" because my box in question is now headless (serial only). Thanks!) Alternative suggestion to test this: If you have a kvm server (headless) you can always run and can ssh to it You can run: virt-viewer -c 'qemu+ssh://<user>@<kvmserver>/system' <vmname> or virt-manager to simulate this behavior. This is still the case for F21 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. This is still the case for fedora 22 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. Bump. This happens to me as well. Dear Friends, I suffer from the same bug in Fedora SecurityLab 23 x86_64. When I use "console=ttyS0,38400n8" everything is perfect. I can type my LUKS password, select kernel, etc. If I add "console=tty0" to the above kernel parameters, I can type my password only on tty0 (virt-viewer) This is still a problem in F23. It's probably still a problem in F24. It's a significant problem for server users who happen to have a graphic head too. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |
Created attachment 901018 [details] plymouth-debug.log * Description of problem: On the kernel command line, I pass console=tty console=ttyS0,115200n8 I have an encrypted (LUKS+LVM) disk (prepared by anaconda). - Plymouth displays the password prompt on both the serial console and the monitor (ie. VT). - When I type on the normal (directly attached, USB) keyboard, the asterisks **** are displayed on both terminals correctly (serial and VT). If I complete the password, the system boots OK. - When I type on the serial console, no asterisks appear on either terminal; keyboard input over serial console is lost. Serial console works correctly in grub2 and at the login prompt; so I can choose both before plymouth and after plymouth what I want to boot and how I want to log in, using either the serial console or the USB keyboard + normal monitor. The problem is that plymouth doesn't let me choose where I want to enter the LUKS password; it forces me to use the USB keyboard. * Version-Release number of selected component (if applicable): plymouth-0.8.9-3.2013.08.14.fc20.x86_64 * How reproducible: 100% * Steps to Reproduce: 1. install F20 with LUKS+LVM (as offered by anaconda) 2. set "console=tty console=ttyS0,115200n8" in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub 3. run grub2-mkconfig -o /boot/grub2/grub.cfg 4. reboot 5. try to enter the LUKS password on the serial console when prompted * Actual results: keyboard input from the serial console has no effect * Expected results: password should be accepted and reported back with **** * Additional info: - I tried enabling verbose mode at the password prompt (using the USB keyboard, Ctrl+V), it didn't help; the serial console remained dead (for input of course; output **** works fine, when typing on the VT). - Attaching debug log.