http://bugzilla.opensuse.org/show_bug.cgi?id=1087925
http://bugzilla.opensuse.org/show_bug.cgi?id=1087925#c8
Michal Srb
Apr 04 19:46:23 virtual1 sddm-greeter[3214]: Socket error: "QLocalSocket::connectToServer: The socket operation is not supported" Apr 04 19:46:23 virtual1 sddm-greeter[3214]: Cannot connect to the daemon - is it running? Apr 04 19:46:23 virtual1 sddm-greeter[3214]: Could not initialize GLX Apr 04 19:46:23 virtual1 kernel: Core dump to |/usr/lib/systemd/systemd-coredump 3214 187 467 6 1522885583 18446744073709551615 sddm-greeter pipe failed
This means sddm-greeter aborted because it could not initialize GLX. If GLX worked, it wouldn't crash.
I don't think the GLX initialization fail is the culprit here. It would be strange that GLX would work without NIS and stopped with it. When sddm-greeter prints the message "Cannot connect to the daemon - is it running?" it calls `QCoreApplication::exit`. Unlike the `exit` function from stdlib, this method does return. It only sets some flag that the application's event loop should not run. So even that sddm-greeter is trying to exit, it still proceeds with initialization and also calls `QGuiApplication::exec()`. Then Qt tries to initialize GLX, but it fails because it did not receive any usable configs. My guess is that it did not receive them because it was in the exiting state. So I think the GLX message is only falloff from sddm-greeter exiting. The main cause is that it failed to talk to sddm. Maybe sddm is busy/frozen/broken because of the NIS? -- You are receiving this mail because: You are on the CC list for the bug.