[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Package changed: nvi (Ubuntu) => nvidia-graphics-drivers-435 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Expired Status in gdm3 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Also affects: nvi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Expired Status in gdm3 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Changed in: gdm3 (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Expired Status in gdm3 package in Ubuntu: Triaged Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
Thanks. If a fix exists in any release (even pre-release) then we mark it as Fix Released. ** Changed in: gdm3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Expired Status in gdm3 package in Ubuntu: Fix Released Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Changed in: gdm Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Expired Status in gdm3 package in Ubuntu: Triaged Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu) Status: New => Triaged ** Bug watch added: GNOME Bug Tracker #787207 https://bugzilla.gnome.org/show_bug.cgi?id=787207 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=787207 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gdm: Unknown Status in gdm3 package in Ubuntu: Triaged Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Summary changed: - no gdm3 greeter with nvidia quadro and modeset=1 + no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gnome-shell package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
