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 1127378 - Login banner disappears upon failed login or after gnome3 screen-shield activation.
Summary: Login banner disappears upon failed login or after gnome3 screen-shield activ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1133060 1205796
TreeView+ depends on / blocked
 
Reported: 2014-08-06 18:56 UTC by amit yadav
Modified: 2019-07-11 08:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-31 13:48:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1155863 0 None None None Never

Description amit yadav 2014-08-06 18:56:34 UTC 
Description of problem:

On boot, the banner is present.  Enter a username (valid or invalid), enter a bad password twice. The login page resets, requesting a username again, but without the banner.

This same thing can be seen by entering a username (valid or invalid) and then clicking "cancel".

Login banner works well until the screen shield starts and rolls down a clock and date display. After that the banner is gone. 

Also it prompts twice for username. Restarting gdm returns the banner.

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

gdm-3.8.4-28.el7_0.1.x86_64
gnome-shell-3.8.4-32.el7_0.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set login banner in RHEL7
2. Enter a username (valid or invalid), enter a bad password twice.
  
   Or Enter username (valid or invalid) and then click "cancel".

   Or Wait for screen shield(screen losk) to start. 

3. After that the banner is gone. 


Actual results:
Banner disappears

Expected results:
Banner should not disappear and it should not ask twice for username.

Additional info:

Tried to disable lock-screen using dconf-editor and gsettings to workaround this issue:

   gsettings set org.gnome.desktop.session idle-delay 0
   gsettings set org.gnome.desktop.lockdown disable-lock-screen true
   gsettings set org.gnome.desktop.screensaver lock-enabled true

Also tried gnome-shell extensions:

  https://extensions.gnome.org/extension/730/curtains-up/
  https://extensions.gnome.org/extension/672/disable-screen-shield/
  
But nothing worked.
Comment 7 Ray Strode [halfline] 2015-03-31 13:48:35 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://rhn.redhat.com/errata/RHSA-2015-0535.html
Note You need to log in before you can comment on or make changes to this bug.