Bug 1295905 - gdm won't start after recent update
Summary: gdm won't start after recent update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-05 18:30 UTC by John Haiducek
Modified: 2020-02-19 20:09 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-19 20:09:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

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!


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