Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1072801

Summary: gdm doesn't start
Product: Red Hat Enterprise Linux 7 Reporter: Petr Lautrbach <plautrba>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: ltinkl, svenkatr, than, vbenes
Target Milestone: rc   
Target Release: 7.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gnome-session-3.8.4-11.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:28:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg none

Description Petr Lautrbach 2014-03-05 09:06:09 UTC 
Description of problem:
kdm was recently removed from rhel-7 in favour of gdm so I've installed gdm, enabled gdm.service and rebooted. But gdm shows only message:
----
Oh no! Somthing has gone wrong.
A problem has occured adn this system can't recover.
Please log out and try again.
----
with button "Log Out".

When I hit the button, the screen goes black and nothing else happens.

journalctl -u gdm.service shows:
Mar 05 09:56:20 myhost systemd[1]: Starting GNOME Display Manager...   
Mar 05 09:56:20 myhost systemd[1]: Started GNOME Display Manager.      
Mar 05 09:56:20 myhost gdm[4645]: Child process 4657 was already dead. 
Mar 05 09:56:20 myhost gdm[4645]: GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed                                                          
Mar 05 09:56:20 myhost gdm[4645]: GLib-GObject: g_object_unref: assertion `object->ref_count > 0' failed                                                        
Mar 05 09:56:20 myhost gdm[4645]: GdmDisplay: display lasted 0.025900 seconds                                                                                   
Mar 05 09:56:21 myhost gdm[4645]: Failed to give slave programs access to the display. Trying to proceed.                                                     

# systemctl status gdm.service                                        
gdm.service - GNOME Display Manager                                                      
   Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
   Active: active (running) since Wed 2014-03-05 09:56:20 CET; 7min ago
 Main PID: 4645 (gdm)
   CGroup: /system.slice/gdm.service
           ├─4645 /usr/sbin/gdm
           ├─4658 /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager...
           └─4663 /usr/bin/Xorg :1 -background none -verbose -auth /run/gdm/auth-for-g...

Mar 05 09:56:20 myhost systemd[1]: Started GNOME Display Manager.
Mar 05 09:56:20 myhost gdm[4645]: Child process 4657 was already dead.
Mar 05 09:56:20 myhost gdm[4645]: GLib-GObject: g_object_ref: asser...d
Mar 05 09:56:20 myhost gdm[4645]: GLib-GObject: g_object_unref: ass...d
Mar 05 09:56:20 myhost gdm[4645]: GdmDisplay: display lasted 0.0259...s
Mar 05 09:56:21 myhost gdm[4645]: Failed to give slave programs acc....
Hint: Some lines were ellipsized, use -l to show in full.

Version-Release number of selected component (if applicable):
gdm-3.8.4-12.el7.x86_64

I've got two screen connected and it uses to worked fine with kdm and still works using
startx.
Comment 1 Petr Lautrbach 2014-03-05 09:07:34 UTC 
Created attachment 870877 [details]
dmesg
Comment 3 Ray Strode [halfline] 2014-03-10 17:04:21 UTC 
presumably you don't have gnome-settings-daemon installed.
Comment 4 Ray Strode [halfline] 2014-03-10 17:43:09 UTC 
hmm we actually already have:

 Requires: gnome-settings-daemon >= 2.21.92

in the spec file. So the only other possibility is missing software GL.  I'll add

 Requires: mesa-dri-drivers

to gnome-session.
Comment 5 Ray Strode [halfline] 2014-03-27 21:27:42 UTC 
I've added an Obsoletes and Provides gdm-user-switch-applet to gdm as well.  See bug 1078271 for more details.
Comment 6 Petr Lautrbach 2014-03-28 11:33:28 UTC 
With the update to gnome-session-3.8.4-11.el7, mesa-dri-drivers-9.2.5-5.20131218.el7.x86_64 was installed and it works for me now. Thanks.
Comment 8 Vladimir Benes 2014-04-28 09:36:13 UTC 
Gdm requires gnome-session which requires mesa-dri-drivers. This guarantees all packages are in place for all setups.
Comment 9 Ludek Smid 2014-06-13 12:28:42 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.