Bug 1339874 - RHEL7.2 Gnome Login screen passwod field could appear upon the user account.
Summary: RHEL7.2 Gnome Login screen passwod field could appear upon the user account.
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.2
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-26 03:39 UTC by fine.fan
Modified: 2020-12-15 07:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-12-15 07:41:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
RHEL7-GNOME-LoginScreenPasswordWrongFunnySteps (457.86 KB, image/png)
2016-05-26 03:39 UTC, fine.fan
no flags Details

Description fine.fan 2016-05-26 03:39:17 UTC
Created attachment 1161706 [details]

Description of problem:

There is a way to get the GNOME login password field appear upon the user account area in the GNOME Login screen.

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


How reproducible:

Steps to Reproduce:
1.Install the RHEL7.2 with "Server with GUI"
2.When the OS boot up and display the GNOME Login screen,
3.Highlight to choose a account then press Enter 
4.Input the wrong password in the password field then press Enter
5.Press the ESC as soon as the yellow "Sorry, that didn't work. Please try again." strings appear.
6.Obsearve the screen .

Actual results:
The password field appear upon the user account area

Expected results:
It may should back to chose a account screen with out any password input field.

Additional info:
Need to press ESC very fast as soon as the Yello "Sorry, that didn't work, Please try again." appear.Some time it will do that operator serval times to see the strange screen.

Comment 3 RHEL Program Management 2020-12-15 07:41:44 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.

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