After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 765197 - Gdm does not start with nvidia driver
Gdm does not start with nvidia driver
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-18 08:43 UTC by dima-gr
Modified: 2018-05-24 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
dmesg.log and journal.log (16.24 KB, application/gzip)
2016-04-18 08:43 UTC, dima-gr
Details
sveinelo journal output. gdm debug (262.96 KB, text/x-log)
2016-06-08 16:29 UTC, sveinelo
Details

Description dima-gr 2016-04-18 08:43:45 UTC
Created attachment 326225 [details]
dmesg.log and journal.log

After installing nvidia driver, gdm does not start.
Installing driver by this article https://wiki.archlinux.org/index.php/NVIDIA_Optimus.

After rebooting - diplay goe's black.
Comment 1 sveinelo 2016-06-08 16:28:07 UTC
I have the same issue. gdm does not start with nvidia blob.

Stack trace of thread 740:
#0  0x00007f9a6420f057 n/a (libmutter.so.0)
#1  0x00007f9a6421b655 n/a (libmutter.so.0)
#2  0x00007f9a64242a5e meta_init (libmutter.so.0)
#3  0x0000000000401ee2 main (gnome-shell)
#4  0x00007f9a622ee741 __libc_start_main (libc.so.6)
#5  0x00000000004022c9 n/a (gnome-shell)

attaching sveinelo_journal.log
Comment 2 sveinelo 2016-06-08 16:29:05 UTC
Created attachment 329406 [details]
sveinelo journal output. gdm debug
Comment 3 Daniel Espinosa 2016-08-24 17:02:13 UTC
I would like to test my self in my box, but I don't know how to recover from this black screen if happened. Could any point me how and recurring testing to see if is fixed?
Comment 4 sveinelo 2016-08-25 21:20:15 UTC
For me there is still an issue with monitor detection.
https://bugzilla.gnome.org/show_bug.cgi?id=768204

I boot into shell. start gdm with:

systemctl start gdm.service

Then I wait a little while to see if stuff works. If screen stays blank:

alt+ctrl+F3

to switch to another terminal. Then stop gdm with

systemctl stop gdm.service

Then I start X with startx. I also check the logs to see if the stack trace has change any.

journalctl -b
Comment 5 K. Pili 2017-08-18 20:16:18 UTC
In my case, I have never been able to get GDM to work with Nvidia drivers since version 3.14, I now have gdm-3.24.2 which I compiled from source along with all the other gnome software. I use Nvidia driver version 384.59 with card GeForce GTX 550 Ti. 

From the logs, I reckon that GdmDisplay is failing to connect to the display. All that happens is some flickering of the black display and keyboard LEDs, then failure. Further failures occur with gdm-launch-environment. There are no error messages in X.log.

For clarity, my other display managers (sddm, kdm, lxdm, xdm) work fine. The exception is lightdm that behaves like gdm. I have also disable Wayland. Lastly, I can launch gnome-shell either from the console or through the other display managers.

----
Aug 18 11:38:24 chui systemd[1]: Starting X Display Manager...
Aug 18 11:38:24 chui gdm[2515]: Enabling debugging
Aug 18 11:38:24 chui gdm[2515]: Changing user:group to gdm:gdm
Aug 18 11:38:24 chui gdm[2515]: Successfully connected to D-Bus
Aug 18 11:38:24 chui gdm[2515]: Getting value of DISPLAYMANAGER_STARTS_XSERVER
Aug 18 11:38:24 chui gdm[2515]: Got value of DISPLAYMANAGER_STARTS_XSERVER: yes
Aug 18 11:38:24 chui gdm[2515]: Getting value of DISPLAYMANAGER_REMOTE_ACCESS
Aug 18 11:38:24 chui gdm[2515]: Got value of DISPLAYMANAGER_REMOTE_ACCESS: no
Aug 18 11:38:24 chui gdm[2515]: GdmManager: GDM starting to manage displays
Aug 18 11:38:24 chui gdm[2515]: GdmLocalDisplayFactory: Adding display on seat seat0
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: id: (null)
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: seat id: (null)
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: session class: greeter
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: initial: no
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: allow timed login: yes
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: local: yes
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: seat id: seat0
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: initial: yes
Aug 18 11:38:24 chui gdm[2515]: GdmDisplayStore: Adding display /org/gnome/DisplayManager/Displays/456040985408 to store
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: Managing display: /org/gnome/DisplayManager/Displays/456040985408
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: Preparing display: /org/gnome/DisplayManager/Displays/456040985408
Aug 18 11:38:24 chui gdm[2515]: doing initial setup? no
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: prepare display
Aug 18 11:38:24 chui gdm[2515]: Getting value of DISPLAYMANAGER_AUTOLOGIN
Aug 18 11:38:24 chui gdm[2515]: Got value of DISPLAYMANAGER_AUTOLOGIN:
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: Got automatic login details for display: 0
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Creating D-Bus server for worker for session
Aug 18 11:38:24 chui gdm[2515]: GdmSession: D-Bus server for workers listening on unix:abstract=/tmp/dbus-A9OXh8SO
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Creating D-Bus server for greeters and such
Aug 18 11:38:24 chui gdm[2515]: GdmSession: D-Bus server for greeters listening on unix:abstract=/tmp/dbus-8wbGqffB
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Setting display device: (null)
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: Running greeter
Aug 18 11:38:24 chui gdm[2515]: GdmDisplay: Creating greeter for (null) (null)
Aug 18 11:38:24 chui gdm[2515]: GdmLaunchEnvironment: Starting...
Aug 18 11:38:24 chui gdm[2515]: GdmLaunchEnvironment: Setting up run time dir /run/gdm/greeter
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Creating D-Bus server for worker for session
Aug 18 11:38:24 chui gdm[2515]: GdmSession: D-Bus server for workers listening on unix:abstract=/tmp/dbus-xS9cn0B8
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Creating D-Bus server for greeters and suchAug 18 11:38:24 chui gdm[2515]: GdmSession: D-Bus server for greeters listening on unix:abstract=/tmp/dbus-fn51RBwk
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Setting display device: (null)
Aug 18 11:38:24 chui gdm[2515]: GdmSession: starting conversation gdm-launch-environment
Aug 18 11:38:24 chui gdm[2515]: GdmSessionWorkerJob: Starting worker...
Aug 18 11:38:24 chui gdm[2515]: GdmSessionWorkerJob: Running session_worker_job process: gdm-session-worker [pam/gdm-launch-environment] /opt/gnome/libexec/gdm/gdm-session-worker
Aug 18 11:38:24 chui gdm[2515]: GdmSessionWorkerJob: : SessionWorkerJob on pid 2520
Aug 18 11:38:24 chui gdm[2515]: GdmLocalDisplayFactory: display status changed: 1
Aug 18 11:38:24 chui gdm-launch-environment][2520]: Enabling debugging
Aug 18 11:38:24 chui gdm-launch-environment][2520]: GdmSessionWorker: connecting to address: unix:abstract=/tmp/dbus-xS9cn0B8
Aug 18 11:38:24 chui gdm[2515]: GdmDBusServer: new connection 0x6a2e293670
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Handling new connection from worker
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Authenticating new connection
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: calling 'ListCachedUsers'
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: Failed to identify the current session: No such device or address
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: seat unloaded, so trying to set loaded property
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: Listing cached users, so not setting loaded property
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: Listing cached users, so not setting loaded property
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
Aug 18 11:38:24 chui gdm[2515]: GdmSession: worker connection is 0x6a2e293670
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Emitting conversation-started signal
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Beginning setup for session for program using PAM service gdm-launch-environment
Aug 18 11:38:24 chui gdm[2515]: GdmSession: Conversation started
Aug 18 11:38:24 chui gdm-launch-environment][2520]: AccountsService: ActUserManager: unrefing manager owned by finished ListCachedUsers call
Aug 18 11:38:24 chui gdm-launch-environment][2520]: GdmSessionWorker: attempting to change state to SETUP_COMPLETE
Aug 18 11:38:24 chui gdm-launch-environment][2520]: GdmSessionWorker: initializing PAM; service=gdm-launch-environment username=gdm seat=seat0
Aug 18 11:38:24 chui gdm-launch-environment][2520]: GdmSessionWorker: Set PAM environment variable: 'XDG_SEAT=seat0'
Comment 6 K. Pili 2017-09-20 20:39:31 UTC
Just and update on this. I figured out part of the problem. My problem was that gdm could not find some files (not sure which). So I had to move my applications, gdm and gnome-session data folders to /usr/local/share. This gets the gdm greeter to launch successfully. The problem now is that I cannot login via gdm.

Firstly, there is no option for any window manager, even after selecting my username. Then, gdm tries whatever it considers to be the default window manager, which results in the error "gdm-x-session ... Cannot open display". This is silly because it was already running on the display, so how did it forget it? Any ideas?
Comment 7 GNOME Infrastructure Team 2018-05-24 11:23:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/258.