(In reply to Wolfgang Bauer from comment #4) > SDDM crashes with a segfault if Xorg cannot be started. I was not really aware about this software behaviour before. Do any more bug reports exist for such a detail? > the main one is that Xorg doesn't start in the first place I am curious about further corresponding failure reasons. > We do not support "special software combinations"... I got an other impression on how automatic quality assurance could eventually improve the situation also around the evolution of components from openSUSE Tumbleweed. (In reply to Wolfgang Bauer from comment #5) > https://build.opensuse.org/package/view_file/KDE:Frameworks5/sddm/0005-Cleanup-dangling-pointer-in-SocketServer-725.patch?expand=1 Thanks for the link. > But I want to repeat: it won't help really, the SDDM segfault (and the fix) I find a bit more software development attention useful also around an issue like ���Cleanup dangling pointer in SocketServer���. https://github.com/sddm/sddm/pull/725 > is just "cosmetical". I imagine that the added destructor can prevent further hiccups, can't it? > If Xorg fails to start, you won't get a graphical interface > or a login greeter. I hope that the next error messages might become easier to handle.