http://bugzilla.opensuse.org/show_bug.cgi?id=1128891 http://bugzilla.opensuse.org/show_bug.cgi?id=1128891#c1 Laurence Page changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ljpage@cwgsy.net --- Comment #1 from Laurence Page --- Very similar problem after zypper dup on 7th March 2019 which still persists after a further (hopeful) zypper dup on 13th March 2019. Also reinstalled SDDM and Nvidia drivers. - SDDM boots to a black screen with a moveable arrow cursor - Xorg.0.log shows similar message: [ 93.415] (EE) Failed to open authorization file "/run/sddm/{8437ebea-d637-497f-a2ee-fdd1e2e3ec6b}": No such file or directory - ls shows that the file does exist: % sudo ls /run/sddm {8437ebea-d637-497f-a2ee-fdd1e2e3ec6b} - ps shows that the filename is being passed to /usr/bin/Xorg via the -auth argument. - Xorg.0.log then shows all input devices being removed I can't see any evidence of SDDM login being active "in the dark". It just seems to have hung. ps doesn't show a greeter process. Graphics system seems to be functioning correctly as logging in with KDM is fine. Relevant software versions: x11-video-nvidiaG05-418.43-9.1.x86_64 nvidia-computeG05-418.43-9.1.x86_64 nvidia-gfxG05-kmp-default-418.43_k4.20.7_1-9.1.x86_64 nvidia-glG05-418.43-9.1.x86_64 sddm-0.18.0-7.1.x86_64 kernel-default-4.20.13-1.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1128891 http://bugzilla.opensuse.org/show_bug.cgi?id=1128891#c4 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fabian@ritter-vogt.de Resolution|--- |FIXED --- Comment #4 from Fabian Vogt --- (In reply to Laurence Page from comment #3)

Thanks John,

I had a look at:

https://bugzilla.suse.com/show_bug.cgi?id=987487

and saw that, following your comment, Fabian Vogt had added one to say that the latest fixed version of sddm was now in the main repo. I therefore thought it best to do another "zypper dup" (1000+ items) before trying your workaround (even though I already had sddm-0.18.0-7.1 installed). Upon reboot sddm is working again (without your workaround).

Good news, so I consider this as fixed. -- You are receiving this mail because: You are on the CC list for the bug.