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 1282577 - gnome hangs when postlogin script fails
Summary: gnome hangs when postlogin script fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.1
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1203710 1297830 1313485
TreeView+ depends on / blocked
 
Reported: 2015-11-16 19:10 UTC by Joe Wright
Modified: 2019-11-14 07:08 UTC (History)
3 users (show)

Fixed In Version: gdm-3.14.2-13.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:39:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2451 0 normal SHIPPED_LIVE gdm bug fix and enhancement update 2016-11-03 14:04:05 UTC

Description Joe Wright 2015-11-16 19:10:02 UTC
Description of problem:
Gnome fails when postlogin script exits with status 1

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

How reproducible:
verified by frontline support

Steps to Reproduce:
1. create /etc/gdm/PostLogin/Default
2. add the line 'exit 1'
3. save changes, make the Default file executable
4. Restart GDM 
5. Attempt GUI login
6. Observe

Actual results:
- Gnome hangs

Expected results:
- Gnome should start normally

Additional info:
- Gnome should not fail when the post login script fails. 
- No errors in debug output when Gnome debugging is enabled

Comment 2 Joel Huddleson 2015-11-16 21:23:44 UTC
Expected results should be changed to:

- Gnome restarts login process

Comment 3 Joel Huddleson 2015-11-16 21:30:59 UTC
(In reply to Joel Huddleson from comment #2)
> Expected results should be changed to:
> 
> - Gnome restarts login process

Incidentally, this expected result *is* the documented behavior for GNOME3.

Comment 4 Ray Strode [halfline] 2016-04-18 20:04:18 UTC
So the behavior changed a bit in RHEL 7.2 since we've rebased to newer GDM.  We no longer hang, but there is still a show stopping problem.

Namely, the login screen in RHEL 7 is not capable of showing windows (including windows created by zenity).

I think the best option is to move the PostLogin/PreSession scripts to get run after the login screen is torn down, immediately before forking to start the session.

Comment 7 Michael Boisvert 2016-09-01 14:23:07 UTC
With the script added, the log in process is restarted and does not hang on gdm-3.14.2-18.el7.

Verified.

Comment 9 errata-xmlrpc 2016-11-04 06:39: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-2016-2451.html


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