I'm seeing what appears to be the same crash on different hardware, which I hope is corroborating evidence that this isn't environment-specific:
Hardware: Intel NUC, onboard Intel HD Graphics 620 (i915 driver) Debian 13 (trixie), fresh install Same secondary "PAM unable to dlopen(pam_sss.so): ... PAM adding faulty module: pam_sss.so" messages appearing alongside the crashes, matching your log. Kernel-logged segfaults in libKF6CoreAddons.so.6.13.0 on four separate occasions over a few days, all at the identical offset reported in the original report (38f1e), e.g.: kernel: kscreenlocker_g[2800]: segfault at 50 ip 00007fba2ad57f1e sp 00007fff370f71d0 error 4 in libKF6CoreAddons.so.6.13.0[38f1e,7fba2ad45000+7e000] likely on CPU 1 (core 1, socket 0) I don't have a full backtrace/core dump from my own occurrences. kscreenlocker_greet disables core dumps without the --testing flag, same as you found, but the matching library, identical crash offset, and the same accompanying PAM error seems to suggest this is the same underlying issue, not a one-off. I don't see this forwarded to KDE's own bug tracker yet and I don't know what the conventions are. I am happy to file it there myself with these details if that would help. Let me know.
