RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1702764 - plymouth luks password string not shown
Summary: plymouth luks password string not shown
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: plymouth
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1681715
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-24 17:12 UTC by Oliver Ilian
Modified: 2020-04-28 16:03 UTC (History)
5 users (show)

Fixed In Version: plymouth-0.9.3-16.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:03:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
dmesg from verbose plymouth (79.96 KB, text/plain)
2019-07-11 09:30 UTC, Oliver Ilian 		no flags Details
plymouth debug log (120.81 KB, text/plain)
2019-07-15 09:52 UTC, Oliver Ilian 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1722 0 None None None 2020-04-28 16:03:26 UTC

Description Oliver Ilian 2019-04-24 17:12:46 UTC 
Description of problem:
When plymouth asks for a luks password, the string below the dialog window is not shown.

"Please enter passphrase for disk ..."

Version-Release number of selected component (if applicable):
RHEL 8
plymouth-0.9.3-12.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. Install an RHEL 8 with an encrypted hard drive
2. boot the system

Actual results:
The text under the dialog is not shown

Expected results:
The text should be shown to inform the user what is expected.

Additional info:
A simple "Please enter your hard drive encryption passphrase" would be 
sufficient 

This is how it currently looks on RHEL 8: https://ryanlerch.fedorapeople.org/Selection_052.png

This is how it looks (similar) on RHEL 7: https://tracker.pureos.net/file/data/jxxtvvessyjlxioywlr4/PHID-FILE-bwmf7kuuplcnn7bcyl3h/pureos-live-unencrypt-disk-prompt-twice.png
Comment 1 Ray Strode [halfline] 2019-04-24 20:25:32 UTC 
i think at some point in rhel 7 we started shipping fonts in initrd. if so, we should do same im rhel 8
Comment 2 Oliver Ilian 2019-04-25 08:02:19 UTC 
Any way I can try this out on RHEL 8 if this is the font issue? I am booting in EFI mode here.
Comment 3 Ray Strode [halfline] 2019-04-25 14:02:30 UTC 
should just be a matter of doing a build with this patch:

https://src.osci.redhat.com/rpms/plymouth/blob/rhel-7.7/f/ship-label-plugin-in-initrd.patch
Comment 13 Ray Strode [halfline] 2019-07-10 18:46:53 UTC 
can you put plymouth.debug=stream:/dev/kmsg on the kernel command line , reproduce, and then attach dmesg ?
Comment 15 Oliver Ilian 2019-07-11 09:30:50 UTC 
Created attachment 1589361 [details]
dmesg from verbose plymouth
Comment 16 Ray Strode [halfline] 2019-07-12 16:46:43 UTC 
sigh

[   31.419577] plymouthd: 990 output lines suppressed due to ratelimiting

can you just do plymouth.debug instead of plymouth.debug=stream:/dev/kmsg and then post /var/log/plymouth.log ?
Comment 17 Oliver Ilian 2019-07-15 09:52:55 UTC 
Created attachment 1590674 [details]
plymouth debug log

I guess you meant /var/log/plymouth-debug.log
Comment 18 Oliver Ilian 2019-07-19 08:44:19 UTC 
any news on this bug?
Comment 19 Ray Strode [halfline] 2019-07-31 17:40:22 UTC 
I still suspect it's not a plymouth issue, but hard to say without reproducing locally. unfortunately the logs with timestamps are missing large chunks (presumably from rate limiting) and the logs without timestamps are missing... timestamps.

moving back to ASSIGNED for now until I can get a chance to reproduce in a vm.
Comment 30 Ivan Molodetskikh 2020-02-19 10:19:53 UTC 
Same issue on a clean F31 install. Just a screen with the prompt and a Fedora logo, and no text saying what this is all about. Also typing in the wrong password doesn't say anything about how it was a wrong password, just drops into the same screen.
Comment 31 Ray Strode [halfline] 2020-02-19 15:43:34 UTC 
that's definitely expected in Fedora at the moment.
Comment 32 Ivan Molodetskikh 2020-02-19 16:01:57 UTC 
Huh? Should I file it as a separate, Fedora bug then? I consider it an issue that there's no explanation on that screen. This is the bug that I came across when searching bugzilla with the goal to file an issue, so I commented here.
Comment 33 Ray Strode [halfline] 2020-02-19 16:53:46 UTC 
It would be appropriate to file a Fedora bug if you'd like to see the behavior changed in Fedora. It might make sense for Fedora to behave the same as RHEL in this case, but I just wanted to point out that the current behavior in Fedora is "by design" (for various reasons...showing text in the initramfs requires adding fonts, font rendering libraries and translations to the initramfs, there shouldn't be any ambiguity over what password is being asked for, so not strictly necessary to be specific, etc, etc).
Comment 35 errata-xmlrpc 2020-04-28 16:03:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1722
Note You need to log in before you can comment on or make changes to this bug.