Bug 471007 - Plymouthd blocks keyboard if rescue booting with init=/bin/bash
Plymouthd blocks keyboard if rescue booting with init=/bin/bash
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: plymouth (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F10DesktopTarget
  Show dependency treegraph
 
Reported: 2008-11-11 06:17 EST by Milan Broz
Modified: 2013-02-28 23:07 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-15 16:27:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Milan Broz 2008-11-11 06:17:53 EST
Description of problem:

If you change GRUB prompt to replace init with the shell
(almost standard rescue procedure when everything fails)

plymouthd blocks keyboard output - no chars (or only something) is shown
in the prompt.

Anyway, is still accepts input, so if you are able to kill plymouthd and reset terminal, it works again.

Version-Release number of selected component (if applicable):

rawhide, plymouth-0.6.0-0.2008.10.30.4.fc10.i386
(encrypted PV, if it has some impact)

How reproducible:
- remove "rhgb quiet" from GRUB parameters and replace with init=/bin/bash
- try to write something when bash shell appears. press enter.

Expected results:
Working rescue shell only. Note that I do not want boot into single user, I need run shell here instead of init (imagine init is broken, udev is broken, etc)
Comment 1 Ray Strode [halfline] 2008-11-11 10:14:04 EST
building a fix for this now

plymouth-0.6.0-0.2008.11.11.1
Comment 2 Will Woods 2008-11-15 16:27:16 EST
This fixed is in current Rawhide plymouth. Please retest and confirm the fix (or reopen the bug if it doesn't work as expected).

Note You need to log in before you can comment on or make changes to this bug.