Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#46769 - [gdm] gdm won't start on boot with nvidia drivers
Attached to Project:
Arch Linux
Opened by Gabriele Musco (gabmus) - Saturday, 17 October 2015, 18:21 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 February 2017, 14:35 GMT
Opened by Gabriele Musco (gabmus) - Saturday, 17 October 2015, 18:21 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 February 2017, 14:35 GMT
|
DetailsDescription:
GDM won't start on boot, even if it's enabled in systemd. This behavior was tested after a clean install. The same issue doesn't seem to happen on my optimus laptop (nvidia gpu disabled by default, the intel integrated one is used instead) so I think it has to be linked to the nvidia proprietary driver. Don't know if it's any useful, but with the previous version of this package, on the same pc, gdm would start, but when logging in, I got gdm background and the cursor, to get to my gnome desktop I had to get to tty2 manually. Probably the two things are relied? It's also worth a mention that after countless reboots at some point gdm started normally, exposing the same "blank background" behaviour described just above, but it didn't show up in the following reboots. When logging into a tty and running "systemctl status gdm" it seemed like gdm was actually up and running, but effectively it wasn't. I was able to start it manually by running "sudo systemctl stop gdm && sudo systemctl start gdm" Additional info: * package version(s): 3.18.0-1 Steps to reproduce: - Install Arch with gdm and nvidia proprietary drivers - reboot and see gdm not starting at boot |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 15 February 2017, 14:35 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#46762
Wednesday, 15 February 2017, 14:35 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#46762?But this doens't even explain why I was able to start GDM manually or even why at some point it started normally. It's something to investigate on for sure. But I'm not quite certain if this needs to be reported to upstream.
Anyway, regarding the Wayland default, I think Arch should stick to Xorg by default for some time. This cannot be reported upstream since GNOME mainly targets fedora, which, as far as I know, doesn't offer the possiblity to install proprietary drivers out of the box.
I did a clean install with nvidia installed. I get stuck on the gdm "blank background" screen regardless of whether I disabled Wayland in /etc/gdm/custom.conf.
When booting most of the time gdm starts but only displays a black screen. Switching to tty2 and restarting gdm from the command line results in the normal gdm screen. After logging in from gdm it gets stuck showing the background and cursor, and switching back to tty2 starts the gnome shell session.
This happens with both nvidia (355) and nvidia-beta (358) from aur. Additionally I'm using glibc recompiled without lock elision to avoid gnome shell crashing with nvidia >= 352 on Skylake CPUs.
FS#46387