Bug 1760775

Summary: [RHEL-7.8]RHEL system account username displays as ciphertext type '***'
Product: Red Hat Enterprise Linux 7 Reporter: Bo Yang <boyang>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.8CC: fmuellner, jadahl, ldu, leiwang, mclasen, rstrode, xinhu, xuli, yacao
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-20 14:27:37 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:
Description Flags
username displays as ciphertext none

Description Bo Yang 2019-10-11 10:08:56 UTC
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.

Comment 2 Bo Yang 2019-10-11 10:17:12 UTC
Created attachment 1624680 [details]
username displays as ciphertext

Comment 3 Bo Yang 2019-10-22 01:11:28 UTC
So, any update about this issue?


BR,
BO

Comment 4 Ray Strode [halfline] 2019-11-20 14:27:37 UTC
fix is known and being proposed

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