Bug 1488708

Summary: RHEL7.4 GNOME login screen "Not listed" doesn't highlighted when selected.
Product: Red Hat Enterprise Linux 7 Reporter: fine.fan <fine.fan>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.4CC: jkoten, mclasen, tpelka
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: 2021-01-15 07:41:50 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
"Not listed ?" item doesn't highlighted when selected it. none

Description fine.fan 2017-09-06 03:26:09 UTC
Created attachment 1322486 [details]
"Not listed ?" item doesn't highlighted when selected it.

Description of problem:
Try to login a GNOME desktop when using RHEL 7.4 with root.
use down arrow to selected "Not listed?" below the general user.
The "Not listed ?" item doesn't highlighted as the previous version, it confuse me if I selected it.

Version-Release number of selected component (if applicable):
rhel-server-7.4-x86_64-dvd.iso

From the .discinfo
1499751070.690815
Red Hat Enterprise Linux 7.4
x86_64

How reproducible:


Steps to Reproduce:
1.Install the OS with the ISO ,use group"Server with GUI"
2.Create a general user during the installation
3.After the installation finished reboot
4.Try to login with root
5.user DownArrow key to select "Not listed ?" from the Login screen
Actual results:
"Not listed ?" item doesn't highlighted. It confuse me if I had selected it ?

Expected results:
"Not listed ?" item does  highlighted.so I can make sure that I am selecting it.

Additional info:

Comment 3 RHEL Program Management 2021-01-15 07:41:50 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.