http://bugzilla.opensuse.org/show_bug.cgi?id=1090122
http://bugzilla.opensuse.org/show_bug.cgi?id=1090122#c1
Max Staudt
In /etc/gdm/custom.conf, if WaylandEnable is set to false, after rebooting and typing login&password into the Gnome login screen, the system hang. I suspect a kernel panic but I don't know what log I can provide to prove it since it seems impossible to switch to a console TTY : ctrl+alt+F1 to F12 doesn't respond once the system is frozen.
Anything to be found in the system journal? Maybe the system had time to write an error message to disk - please use journalctl to have a look. On the other hand, maybe the X server hung, but the system itself is still alive, and VT switching is dead because X and GDM (or maybe earlier: Plymouth and GDM) are fighting for VT_SETMODE and produce a deadlock in the VT subsystem. Been there before.
For your info, I need to fallback to Xorg because Wayland doesn't detect my external screen (I haven't had time to look for troubleshoot tips yet but I may open a bug report in a few days).
Sigh. That's something for the desktop team, I guess.
CPU: Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB
Kaby Lake - that's pretty darn new. I suspect all display outputs are connected to the Intel GPU. Once the Nvidia card is blocked, things should "just work".
Graphics: Card-1: Intel Device 591b Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile]
Whoops. By default, the nouveau kernel driver is in use, which is known to do funky things with some cards. Can you please blacklist the nouveau kernel module, rebuild the initramfs (by calling mkinitrd) and then reboot? Maybe that'll fix it... You can use lsinird to check that nouveau.ko is not contained in the resulting initramfs. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.