Bug 1295905

Summary:	gdm won't start after recent update
Product:	Red Hat Enterprise Linux 7	Reporter:	John Haiducek <jhaiduce>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED NOTABUG	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-19 20:09:24 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:

Description John Haiducek 2016-01-05 18:30:36 UTC

Description of problem:
I updated my system, and gdm no longer starts. I am still able to run gnome using the startx command.

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

How reproducible:
Every time

Steps to Reproduce:
1. Boot system

Actual results:
gdm tries to start but displays a generic (graphical) error screen

Expected results:
gdm should display a login prompt

Additional info:

I am using the nvidia driver from elrepo (kmod-nvidia-352.63-1.el7.elrepo.x86_64). 

I found the following in /var/log/gdm/:0-greeter.log:

X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 24
Current serial number in output stream: 25
gnome-session-check-accelerated: Helper exited with code 256
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 24
Current serial number in output stream: 25
gnome-session-check-accelerated: Helper exited with code 256

Comment 2 Ray Strode [halfline] 2020-02-19 20:09:24 UTC

Apologies for the extremely late reply to this report.  It seems like, perhaps, the nvidia drivers were improperly installed. I hope in the interveaning 4 years you go this working!