Comment # 2 on bug 964812 from John Pemberton

Even though naturally this ticket is of low priority,
since my original statement implied I would provide
updated information, and it's been quite a long time
between then and now, I do apologize since I let
so much time go by before providing the information
I suggested that I would.  I had usually been using KDE,
but I had reasons to at least temporarily switch to Gnome,
and so I didn't think much more about issues with KDE
in all this time, until now.

The original issue was discovered after I did an "upgrade"
install, to "upgrade" from openSUSE 13.2 to Leap 42.1.

In my original comment I mentioned that BOTH the check boxes
to enable screen locking and to require a password
after a specific period were unchecked.  In the
initial use of the original upgrade install, BOTH items
had an associated check box.

Strange though it may seem, during some subsequent uses
of the upgrade install, only the selection to enable screen
locking had an associated check box, AND when I did a "new"
installation of Leap 42.1, not an upgrade, even the first
use immediately after the install had the only one check box,
that for enabling screen locking.  I can only guess there was
some issue with the check boxes relating to the upgrade.

With the upgrade install, after I did the chmod on "kcheckpass"
it worked reliably to validate the password after screen locking.

In the new installation I didn't need to do the chmod on
/usr/lib64/libexec/kcheckpass as mentioned in ticket 931296,
kcheckpass worked just fine without that.

Recently I made a point of repeatedly testing screen locking on
the new install, and it reliably worked as configured, and without
any problems validating the proper password; it worked in a completely
consistent manner.

I hope this helps.