[Bug 1209081] New: [SDDM] SDDM black screen
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 Bug ID: 1209081 Summary: [SDDM] SDDM black screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs@suse.de Reporter: socvirnyl.estela@gmail.com QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Created attachment 865395 --> http://bugzilla.opensuse.org/attachment.cgi?id=865395&action=edit Log for everything from boot to sddm greeter. === SETUP === I have installed the NVIDIA driver `nvidia-driver-G06-kmp-default`. My grub config contains the following line ``` GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-uuid/03f59f3a-97c3-4f83-b63b-53898f15585e mitigations=off quiet security=apparmor nouveau.modeset=0 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau nvidia_drm.modeset=1 nosimplefb=1" ``` So I enabled the nvidia modesetting here. I have a custom xorg config at `/etc/X11/xorg.conf.d` with a file named as `10-nvidia-drm-outputclass.conf` ``` Section "OutputClass" Identifier "intel" MatchDriver "i915" Driver "modesetting" EndSection Section "OutputClass" Identifier "nvidia" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" Option "PrimaryGPU" "yes" ModulePath "/usr/lib/nvidia/xorg" ModulePath "/usr/lib/xorg/modules" EndSection ``` My laptop is an Acer Nitro 5: ``` CPU: Intel(R) Core(TM) i5-10300H (8) @ 4.5 GHz GPU 1: Intel UHD Graphics GPU 2: NVIDIA GeForce RTX 3060 Mobile / Max-Q ``` === ISSUE === Recent updates of SDDM has some issues. I am not sure if this is caused by NVIDIA modesetting on or even SDDM itself. Before I installed NVIDIA since this is a fresh install, there were no issues with blackscreen sddm. === Workaround === Running `systemctl restart --now display-manager.service` enables sddm to run successfully. However, there are still known issues. Sometimes, when switching between ttys, the greeter is full black, **BUT YOU CAN STILL LOGIN IF YOU KNOW WHERE THE PASSWORD PROMPT IS**. === LOGS === I have logs attached below `journalctl-final-2.log -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c1 --- Comment #1 from Soc Virnyl Estela <socvirnyl.estela@gmail.com> --- I think this part of the log is very suspicious. ``` Mar 09 10:48:06 localhost.localdomain kernel: show_signal_msg: 52 callbacks suppressed Mar 09 10:48:06 localhost.localdomain kernel: sddm-greeter[1667]: segfault at 10 ip 0000564d27511a30 sp 00007ffd4009f9a0 error 4 in sddm-greeter[564d274fa000+1d000] likely on CPU 5 (core 1, socket 0) Mar 09 10:48:06 localhost.localdomain kernel: Code: 00 00 48 81 c4 a8 00 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 89 c7 49 89 c6 48 8d 5c 24 30 e8 80 8f fe ff <41> 0f b7 4e 10 45 0f b6 4e 13 48 89 c7 41 8b 46 08 45 0f b6 46 0f Mar 09 10:48:06 localhost.localdomain systemd[1]: Created slice Slice /system/systemd-coredump. Mar 09 10:48:06 localhost.localdomain systemd[1]: Started Process Core Dump (PID 2258/UID 0). Mar 09 10:48:06 localhost.localdomain systemd[1]: Started Process Core Dump (PID 2259/UID 0). Mar 09 10:48:06 localhost.localdomain systemd-coredump[2260]: Process 1667 (sddm-greeter) of user 464 dumped core. Stack trace of thread 1667: #0 0x0000564d27511a30 _ZN4SDDM18XcbKeyboardBackend10initLedMapEv (sddm-greeter + 0x2ca30) #1 0x0000564d27513178 _ZN4SDDM13KeyboardModelC1Ev (sddm-greeter + 0x2e178) #2 0x0000564d27513ccb _ZN4SDDM10GreeterAppC2EP7QObject (sddm-greeter + 0x2eccb) #3 0x0000564d274fe8b8 main (sddm-greeter + 0x198b8) #4 0x00007f880e22caf0 __libc_start_call_main (libc.so.6 + 0x27af0) #5 0x00007f880e22cbb9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27bb9) #6 0x0000564d274ffef5 _start (sddm-greeter + 0x1aef5) ELF object binary architecture: AMD x86-64 Mar 09 10:48:06 localhost.localdomain systemd[1]: systemd-coredump@0-2258-0.service: Deactivated successfully. Mar 09 10:48:06 localhost.localdomain sddm-helper[1656]: [PAM] Closing session Mar 09 10:48:06 localhost.localdomain sddm-helper[1656]: pam_unix(sddm-greeter:session): session closed for user sddm Mar 09 10:48:06 localhost.localdomain sddm-helper[1656]: [PAM] Ended. Mar 09 10:48:06 localhost.localdomain systemd[1]: session-1.scope: Deactivated successfully. Mar 09 10:48:06 localhost.localdomain systemd-logind[1157]: Session 1 logged out. Waiting for processes to exit. Mar 09 10:48:06 localhost.localdomain systemd-logind[1157]: Removed session 1. Mar 09 10:48:06 localhost.localdomain systemd-coredump[2261]: Process 1387 (Xorg.bin) of user 0 dumped core ``` -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c2 --- Comment #2 from Soc Virnyl Estela <socvirnyl.estela@gmail.com> --- I saw a similar issue but it's kind of a different setup? the issue im seeing is boo1206863 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c3 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |socvirnyl.estela@gmail.com Flags| |needinfo?(socvirnyl.estela@ | |gmail.com) --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- Could you attach X logfile, please? It's either /var/log/Xorg.0.log or ~/.local/share/xorg (the latter of the user who tries to log in). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c4 --- Comment #4 from Stefan Dirsch <sndirsch@suse.com> --- BTW, your setup (xorg.conf.d snippet) is nothing we can support. Maybe you can use suse-prime instead, i.e. run 'prime-select' after installing it (if package not installed yet). JFYI, nouveau driver is already blacklisted when using our nvidia KMP. Also modeset is turned on. I'm not sure about the consequences of using 'security=apparmor'. I never tried this with the nvidia driver. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gfx-bugs@suse.de |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c5 --- Comment #5 from Soc Virnyl Estela <socvirnyl.estela@gmail.com> --- Created attachment 865405 --> http://bugzilla.opensuse.org/attachment.cgi?id=865405&action=edit Xorg.0.log for SDDM bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c6 --- Comment #6 from Soc Virnyl Estela <socvirnyl.estela@gmail.com> --- (In reply to Stefan Dirsch from comment #4)
BTW, your setup (xorg.conf.d snippet) is nothing we can support. Maybe you can use suse-prime instead, i.e. run 'prime-select' after installing it (if package not installed yet).
JFYI, nouveau driver is already blacklisted when using our nvidia KMP. Also modeset is turned on.
I'm not sure about the consequences of using 'security=apparmor'. I never tried this with the nvidia driver.
The `security=apparmor` thingy is from the default installation. So I assumed that it's okay to have it there. It's a fresh install. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c7 --- Comment #7 from Soc Virnyl Estela <socvirnyl.estela@gmail.com> --- Turns out using suse-prime solved the problem. I am not so used how the zypper-installed NVIDIA works since I used to use the "Hard Way" method that's why you have seen that GRUB linux exec line plus that nvidia drm outputclass which does the same thing as prime. I guess I will close this issue then as RESOLVED? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209081 http://bugzilla.opensuse.org/show_bug.cgi?id=1209081#c8 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(socvirnyl.estela@ | |gmail.com) | --- Comment #8 from Stefan Dirsch <sndirsch@suse.com> --- Yes, we can close this if it works with suse-prime. Sorry, I wasn't aware that we meanwhile have "security=apparmor" as default. Apparently it wasn't the issue here. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com