http://bugzilla.opensuse.org/show_bug.cgi?id=1160995
http://bugzilla.opensuse.org/show_bug.cgi?id=1160995#c35
Fabian Vogt
To us, the problem with kscreenlocker crashing seems solved or circumvented. It did not happen again since we changed NIS and name server configuration like reported in my last comment. (And we were installing two new machines with openSUSE Leap 15.1 per week since some months.)
Nevertheless, I am still wondering:
If it was a problem with NIS configuration, why did it only affect the kscreenlocker program and nothing else?
I guess that the sandbox also prevented access to nscd, which might have an effect on this.
And if it was caused by our system configuration, why did it only affect a few users? We manage all users in NIS and all accounts are set up the same way.
Can't tell for sure. Maybe also related to caches.
If you like to further examine this or do some more troubleshooting, I would be happy to support you. I also currently do have a workstation dedicated to experiments like this.
As with fixed kscreenlocker and fixed configuration it appears to be working fine now, I'd say that there's no need for further investigation. -- You are receiving this mail because: You are on the CC list for the bug.