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 1217157 - login banner placement checks fail to properly detect text overflow
Summary: login banner placement checks fail to properly detect text overflow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1133060
TreeView+ depends on / blocked
 
Reported: 2015-04-29 16:34 UTC by Matthew Gyurgyik
Modified: 2019-08-15 04:32 UTC (History)
7 users (show)

Fixed In Version: gnome-shell-3.14.4-10.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:19:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/etc/dconf/db/gdm.d/01_banner (1.12 KB, text/plain)
2015-04-29 16:34 UTC, Matthew Gyurgyik
no flags Details
GDM at 1280x800 (407.43 KB, image/png)
2015-04-29 16:35 UTC, Matthew Gyurgyik
no flags Details
GDM at 1440x900 (423.91 KB, image/png)
2015-04-29 16:35 UTC, Matthew Gyurgyik
no flags Details
Screenshot of GNOME-3.14.4 in Fedora 21 (285.50 KB, image/png)
2015-05-11 16:27 UTC, Michal Domonkos
no flags Details
banner screenshot (525.92 KB, image/png)
2015-07-29 21:07 UTC, Joe Wright
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

Description Matthew Gyurgyik 2015-04-29 16:34:20 UTC
Created attachment 1020256 [details]
/etc/dconf/db/gdm.d/01_banner

Description of problem:

The banner message is displayed in two different places depending on the resolution.

Location 1: Banner message is on the left hand side of the screen, user/pass text entry box is on the left hand of the screen. (1280x800)

Location 2: Banner message is above the user/pass text entry box. And the user/pass text entry box is centred on the screen. (1440x900, 1680x1050)



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

$ rpm -qa gdm
gdm-3.8.4-32.el7.x86_64


How reproducible:
Always


Steps to Reproduce:
$ create /etc/dconf/db/gdm.d/01_banner (see attached)
$ dconf update


Expected results:
The banner should be displayed in the same location regardless of display resolution.

Comment 1 Matthew Gyurgyik 2015-04-29 16:35:09 UTC
Created attachment 1020257 [details]
GDM at 1280x800

Comment 2 Matthew Gyurgyik 2015-04-29 16:35:43 UTC
Created attachment 1020258 [details]
GDM at 1440x900

Comment 3 Matthew Gyurgyik 2015-04-29 16:52:38 UTC
Errata RHSA-2015-0535 states "* Prior to this update, only a small area was available on the GDM login screen for a custom text banner. As a consequence, when a long banner was used, it did not fit into the area, and the person reading the banner had to use scrollbars to view the whole text. With this update, more space is used for the banner if necessary, which allows the user to read the message conveniently. (BZ#1110036)"

It sound like this change may be related to this problem. Sadly, BZ#1110036 is private and I can not view it.

Comment 5 Ray Strode [halfline] 2015-05-04 14:56:11 UTC
Hi, showing two different layouts depending on screen resolution and message length is actually "by design".  The idea is to only show short messages above, and show long messages on the side.

Clearly, in your case, the message should be on the side in both situations, though.

Comment 7 Michal Domonkos 2015-05-11 16:25:01 UTC
It looks like this wasn't fixed in GNOME-3.14 in its entirety.

Now the text seems to never overflow any more, however, it's always placed on top of the user list, spanning the whole screen horizontally and that doesn't seem to change with the resolution either (screenshot attached).

Comment 8 Michal Domonkos 2015-05-11 16:27:13 UTC
Created attachment 1024275 [details]
Screenshot of GNOME-3.14.4 in Fedora 21

Comment 9 Michal Domonkos 2015-06-02 09:47:20 UTC
On GNOME-3.16 (Fedora 22), I no longer see the issue I had in comment 7.  The banner always sticks to the side of the user list as it should.

Comment 15 Joe Wright 2015-07-29 21:07:11 UTC
Created attachment 1057420 [details]
banner screenshot

Comment 20 errata-xmlrpc 2015-11-19 07:19:20 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/RHBA-2015-2216.html


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