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.

Description of Problem:
    RHEL system account Username displays as ciphertext type '***' when login system from “Not Listed”.


Version-Release number of selected components (if applicable):
    RHEL Version: RHEL7.8-20191009.6
    GNOME Shell 3.28.3


How reproducible:
    100%

Steps to Reproduce:
    1. Setup an account “rhel” and root password during installing a VM with RHEL7.8-20191009.6 build.
    2. After complete installation, click “Not Listed?” to login with root account.
    3. When input “root” in “Username”, check its display type.


Actual Results:
    1. After step 3, RHEL system account “Username” uses ciphertext type.


Expected Results:
    1. After step 3, RHEL system account “Username” should use plaintext type.

Created attachment 1624680 [details]
username displays as ciphertext

So, any update about this issue?


BR,
BO

fix is known and being proposed

*** This bug has been marked as a duplicate of bug 1772896 ***