http://bugzilla.opensuse.org/show_bug.cgi?id=1087925
http://bugzilla.opensuse.org/show_bug.cgi?id=1087925#c10
--- Comment #10 from Fabian Vogt
(In reply to Fabian Vogt from comment #7)
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.
It's also strange that sddm-greeter is unable to create a socket...
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.
Yes, this is a bug, but GLX initialization should still succeed after that. I verified that on several systems. (In reply to Michal Srb from comment #9)
(In reply to Giacomo Comes from comment #2)
Apr 04 11:33:27 virtual1 sddm-greeter[3561]: Socket error: "QLocalSocket::connectToServer: The socket operation is not supported"
If I am reading the Qt code correctly, in this situation it can happen only if a call to `socket(PF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0)` returned -1. This could happen for various reasons, for example exhausted system resources. (Maybe the NIS client is creating huge amount of sockets?) It would be good to know what was the errno after this call failed.
It's probably the same reason why GLX failed - maybe too many open fds?
Giacomo, could you run sddm in strace? For example after ssh-ing in as root from another machine and running: # systemctl stop display-manager # strace -f -o /tmp/sddm.strace sddm
The please attach the sddm.strace here.
Yes, that would be very useful. Also please provide the output of ps -ef | grep sddm during the black screen. -- You are receiving this mail because: You are on the CC list for the bug.