SUMMARY Since some recent upgrade (`zypper dup`) when logging out, it _may_ happen, that instead to facing SDDM, only a black screen with working cursor shows up. ``` 13:03:19 dbus-daemon[2059]: [session uid=1000 pid=2059] Successfully activated service 'org.kde.Shutdown' 13:03:19 kded5[2250]: X connection to :1 broken (explicit kill or server shutdown). 13:03:19 kaccess[2429]: The X11 connection broke (error 1). Did the X11 server die? 13:03:19 systemd[1993]: app-kaccess@autostart.service: Main process exited, code=exited, status=1/FAILURE 13:03:19 systemd[1993]: app-kaccess@autostart.service: Failed with result 'exit-code'. 13:03:19 kwin_wayland[2077]: QtDBus: cannot relay signals from parent QObject(0x55e8460d68f0 "") unless they are emitted in the object's thread QThread(0x55e845f5f108 "libinput-connection"). Current thread is QThread(0x55e845d9d060 ""). 13:03:19 xdg-desktop-por[2107]: Error reading events from display: Datenübergabe unterbrochen (broken pipe) 13:03:19 kded5[2195]: The Wayland connection broke. Did the Wayland compositor die? ``` Unfortunately I do not have any more hints. Coredumpctl does not report any related crash dump. I can still login in a different tty, but it seems all I can do to recover is to reboot. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230411 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-1-default (64-bit) Graphics Platform: Wayland SDDM: 0.19.0-10.1
*** This bug has been marked as a duplicate of bug 467547 ***
(In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 467547 *** Unfortunately not. Only Fedora was affected by bug 467547 (due to PAM configuration) and on top of that the sddm-0.19.0-10.1 package in openSUSE has the fix.
Well, after having faced the issue several times across multiple reboots, it seems now to have gone (openSUSE Tumbleweed 20230413).