Hi,

Spec;
Fedora 21
KDE 4.14.
kde-workspace-4.11.15-3.fc21.x86_64

I'm new to KDE (KDE 4.14.4) and would really love some advice on how to diagnose this issue I'm having the lockscreen for KDE 4.14.
Issue: Lockscreen works correctly for a while and then suddenly won't accept the correct password any more?!

1. Should log failures be going to /var/log/secure?
2. Is there a known bug perhaps with this version of kde-workspace?
I've only been able to work around the problem by killing the ksmserver and logging in again.


cya

Craig

* does the lockscreen reflect your input (ie. print some nifty dots or asterisks)?
* is you kbd an ascii/qwerty layout or something different?
* Does the password contain "special" chars, that eg. require modifiers (AltGr or even just Shift) resp. would be found in different positions on a qwerty keyboard (eg. in german layouts y & z are swapped)?

Thanks for advice;
* does the lockscreen reflect your input (ie. print some nifty dots or asterisks)?
Yes it does, it accepts the keyboard entries and then fails to accept the password.

* is you kbd an ascii/qwerty layout or something different?
standard Microsoft Digital Media Keyboard (qwerty)

* Does the password contain "special" chars, that eg. require modifiers (AltGr or even just Shift) resp. would be found in different positions on a qwerty keyboard (eg. in german layouts y & z are swapped)?
Just "shift" from your list, we can try changing the password and/or keyboard, it just doesn't make a lot of sense because it does work for a period of time and then suddenly stops working.
Is there a debug or error log for KDE I should be looking at?

The locker should be using PAM for credential handling, so you'll have to activate pam warnings[1] and maybe even debug[2] for the relevant actions.

The relevant config should be /etc/pam.d/kscreensaver (you do likely NOT want to invoke pam_deny)

[1] http://www.linux-pam.org/Linux-PAM-html ... _warn.html
[2] http://www.linux-pam.org/Linux-PAM-html ... debug.html

My guess would be that after the lock (and suspend?) the keyboard gets "reattached" and the layout isn't correct (ie. you don't type what you think that you type - but that's just a wild guess)

Just to be sure: the system presents you with another greeter - it's not that things turn black and you just cannot do anything anymore on that console, is it?

>> it's not that things turn black and you just cannot do anything anymore on that console, is it?
Everything looks fine and the user can still enter in a password. Heres the odd part, we have done a lot of testing on this. Sometimes it does accept the password after 3-5 attempts, other times not at all (ok we stop after about 15 attempts). We are running Redhat IPA Central Auth, so perhaps something odd is going on here too. I'll create the user a local account and see if this solves the issue also. Thanks for the help!

cya

Craig