I’ve just moved from Leap 42.3 to Tumbleweed (fresh install) now that it has an nVidia repo. At first it was okay, but as I put everything back in place then I’ve found I can’t log in to Gnome successfully. Unfortunately, I didn’t get Snapper working until after login broke.
Boot normally, Gnome login manager comes up, pick user, type password, screen goes black (not even a cursor), can’t Ctrl+Alt+F#, have to use SysReq to reboot. Ditto for IceWM (so it isn’t just a Gnome thing)
Edit boot to add “init 3”, log in at command-prompt, run “sudo systemctl start display-manager”, everything is fine and I can log in normally
Remove nVidia binary drivers, reboot, screen flickers quickly between TTY login and the " OK ] …" lines from the boot process, typing doesn’t work reliably because of the flicker so I can’t log in
Do “zypper dup”, nVidia drivers come back automatically, add “nouveau.modeset=0” based on suggestions online (in case Grub is doing something that the GDM can cope with but the desktops can’t), still get black screen after login
The main things that I can see in the log are a warning about “NVRM” and how the NVIDIA drivers don’t support text-mode VGA and “NVIDIA(GPU-0): Failed to acquire modesetting permission” closely followed by “Screen(s) found, but none have a usable configuration.”
Any suggestions on what I can do to debug/fix?
(I’ve got one nVidia 1050Ti running HDMI to my monitor, latest kernel and proprietary drivers, full “zypper dup” about 20 minutes ago, Gnome desktop)
I saw that thread, but it appears to be a different problem. I get the GDM but no login session (and no mouse after I log in), I’ve always been using GDM rather than lightdm, I seem to get it with systems that don’t use Wayland, and none of the logs appear to be similar.
I’ll give it a try the next time I reboot, but most of their reported symptoms are closer to the other thread than mine. I don’t get a mouse when I log in, everything still breaks when I do “init 5” (but not when I restart X or init 3 and then “systemctl start display-manager”), and I can’t drop to a TTY (which I assume is what they meant by “hotkey to a console window”).
Nope, that didn’t fix it. Removing “splash=silent” from the linuxefi line did, though. I’m not sure how that alters its behaviour, but it does. Also, the problem seems to be consistently detectable by Ctrl+Alt+F# not working - I don’t need to try and log in and have it free so that I can only do an emergency SysReq reboot, I can just see whether I can switch TTY and if I can’t then it’s a broken boot.
I don’t suppose that triggers any ideas for anyone, does it?
Something seems to have changed in all of the updates that has fixed this. After forgetting to edit Grub at boot, I noticed that I had access to the TTYs and was able to log in without restarting X or anything.
Oddly, I only get “Gnome” in the login options, though. There’s no “Gnome on X” to differentiate it from Wayland (and “ps aux” shows a couple of X servers running on tty3 and tty7)
Yeah, type is “x11”. I guess that means that my problem is only half-gone - it’s not breaking things with a black screen after login, but it is dropping the GDM into an X11 session so that it can’t run Wayland.
Never mind, it’s not the end of the world, I guess. At least I can let it boot normally and log in now!
Well, as far as I can tell, if wayland is not explicitly disabled and /usr/bin/Xwayland exists gdm goes wayland. And /usr/bin/Xwayland should be dependency of gnome-session-wayland. So a) does /usr/bin/Xwayland exist and b) what is value of daemon/WaylandEnable in /etc/gdm/custom.conf?