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 1470340 - gdm restarts X without waiting for previous generation to terminate
Summary: gdm restarts X without waiting for previous generation to terminate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1469755
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-12 18:45 UTC by Tom Lavigne
Modified: 2017-08-01 11:29 UTC (History)
11 users (show)

Fixed In Version: gdm-3.22.3-12.el7
Doc Type: Bug Fix
Doc Text:
Previously, due to a race condition in logout handling, the GNOME Display Manager (GDM) in some cases started one X server while another was shutting down. Consequently, the second X server failed to start. With this update, GDM waits for the first X server to fully quit before GDM starts the second X server, which prevents the described problem from occurring.
Clone Of: 1469755
Environment:
Last Closed: 2017-08-01 11:29:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2328 0 normal SHIPPED_LIVE gdm bug fix update 2017-08-01 15:26:10 UTC

Description Tom Lavigne 2017-07-12 18:45:48 UTC 
This bug has been copied from bug #1469755 and has been proposed
to be backported to 7.4 z-stream (EUS).
Comment 6 Michael Boisvert 2017-07-18 14:19:49 UTC 
Joseph, did you mean to switch this from VERIFIED to ON_QA?
Comment 7 Joseph Kachuck 2017-07-18 17:26:39 UTC 
Hello Michael,
No would you be able to switch it to verified?

Thank You
Joe Kachuck
Comment 8 Michael Boisvert 2017-07-18 18:27:11 UTC 
(In reply to Joseph Kachuck from comment #7)
> Hello Michael,
> No would you be able to switch it to verified?
> 
> Thank You
> Joe Kachuck

Not a problem. I assumed it was a mid air collision based on the time stamps.
Comment 9 errata-xmlrpc 2017-08-01 11:29:41 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://access.redhat.com/errata/RHBA-2017:2328
Note You need to log in before you can comment on or make changes to this bug.