Description of problem: As kcheckpass is not setuid root, it cannot authenticate using a LDAP server. This is a problem as once the screen is locked, it cannot be unlocked. See the bug report I initially reported @ http://bugs.kde.org/show_bug.cgi?id=126152 . Version-Release number of selected component (if applicable): kdebase-3.5.2-0.2.fc5 How reproducible: Always Steps to Reproduce: 1. setup a LDAP authentification on the server 2. login w/ KDE as a user from the LDAP directory 3. lock your screen, you can't unlock it Actual results: You have to restart X. Expected results: The screensaver should disappear Additional info: It works after: chmod +s `which kcheckpass`
it's now fixed in kdebase-3.5.2-4. It will be available in rawhide soon. The fix also will be included in next kdebase rebuild for FC5 update. Thanks for your report.
FC5 update (kdebase-3.5.2-0.3.fc5) is broken and does not contain kcheckpass as all! $ rpm -q kdebase kdebase-3.5.2-0.3.fc5 $ rpm -ql kdebase | grep kcheckpass /etc/pam.d/kcheckpass $ Result is that it's not possible to unlock screen saver and one has to manually kill kdesktop_lock as suggested by error message.
I confirm this as well!
it seems a packacking bug in kdebase that kcheckpass was not included in this version. I will push new kdebase packacge in FC5 update ASAP which resolves this issue. Thanks for your report.