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 1690023 - double password asterisks and boot log messages in the "details" theme
Summary: double password asterisks and boot log messages in the "details" theme
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: plymouth
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-18 15:25 UTC by Laszlo Ersek
Modified: 2019-08-06 12:38 UTC (History)
2 users (show)

Fixed In Version: plymouth-0.8.9-0.32.20140113.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:38:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 104353 0 None None None 2019-03-18 15:25:11 UTC
Red Hat Bugzilla 1554148 0 unspecified CLOSED solar theme aborts 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2019:2044 0 None None None 2019-08-06 12:38:55 UTC

Description Laszlo Ersek 2019-03-18 15:25:12 UTC
*** Description of problem:

- The "details" theme of Plymouth shows duplicated asterisks when the user is entering the LUKS password (that is, two "*" characters per password character). 

- In addition, boot log messages are shown twice.

- Furthermore, both in the "details" theme and in the default "charge" theme, a partially entered password cannot be completely deleted with Ctrl+U: a number of placeholder characters remain. (It is not deterministic how many remain -- the longer the password is when Ctrl+U is pressed, the higher the chance for some placeholder characters to remain.)

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

plymouth-0.8.9-0.31.20140113.el7.x86_64 (= both RHEL-7.5 and RHEL-7.6)

*** Additional info:

This issue may have been fixed in upstream Plymouth and Fedora's Plymouth:

https://unix.stackexchange.com/questions/369454/boot-time-service-startup-messages-are-repeated-a-second-time
https://bugs.freedesktop.org/show_bug.cgi?id=104353
https://bugzilla.redhat.com/show_bug.cgi?id=1554148

Comment 2 Ray Strode [halfline] 2019-03-26 19:19:02 UTC
So this actually ended up needing this fix:

https://gitlab.freedesktop.org/plymouth/plymouth/commit/059390ac569798cbf40a958ea714b15f313b46a3

(the other one was already in place and dealt with graphical display, not text display)

Comment 5 Laszlo Ersek 2019-05-12 15:25:08 UTC
"plymouth-0.8.9-0.32.20140113.el7" works fine for me, thank you.

Comment 7 errata-xmlrpc 2019-08-06 12:38:30 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-2019:2044


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