Red Hat Bugzilla – Bug 575771
Authentication failed message is cut off with plain gdm login greeter (/usr/libexec/gdmlogin)
Last modified: 2012-02-21 01:45:23 EST
Created attachment 401726 [details] screen shot Description of problem: Problem with resizing of widgets when failed authentication message is displayed for user. Version-Release number of selected component (if applicable): 2.16.x How reproducible: always Steps to Reproduce: 1. Set plain greeter for the system either with gdmsetup or by editing /etc/gdm/custom.conf file as below [daemon] Greeter=/usr/libexec/gdmlogin 2. Now try to login to the system with incorrect password. Actual results: the "Incorrect username or password" message has couple of lines. All what is displayed is "Incorrect username or password. Letters" the rest of the lines are cut off. Expected results: Should not be cutt-off Additional info: gdm-plain.jpg image showing actual issue, and patch attached.
Created attachment 401728 [details] patch based on upstream code From upstream * Do not set size request for Message and error label widgets so they grow if the message is too big. Do not initialize message label to "Please enter your username" since there is no reason to assume that the first PAM request will ask for username. Do not reselect user if chosen from face browser because now we manage this in daemon/verify-pam.c.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
devack+
RHEL5.8 with gdm-2.16.0-59.el5. Setting style to "plain" and logging using an incorrect password I can see the entire message without being cut off. Verified.
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. http://rhn.redhat.com/errata/RHBA-2012-0282.html