Version: RC1 (using KDE 4.0.98) Installed from: Compiled From Sources Compiler: cmake version 2.4-patch 6 OS: Linux KDE 4.1 RC1 Linux Distro: Slackware 12 Compiled from sources using the qt-copy trunk version 4.0.0 The problem seems to appear in my distro from KDE 4.0 to 4.1 RC1. When the session is locked with the Lock/Logout button, the session cannot be unlocked with a correct password. I have take into consideration Caps lock. The password is all in lowercase without numbers or special characters. The user at that moment was kde-delvel.
Please check the user has the possibility to authenticating, as explained in http://techbase.kde.org/Getting_Started/Build/KDE4/Troubleshooting#Locked_sessions
I tried the troubleshooting but does not seem to work. I did: 1. chmod 755 $KDEDIR/lib/kde4/libexec/kcheckpass 2. I did not had PAM 3. Install Linux-PAM-1.0.1 (Configure - Make - Make test - Install) All Fine 4. Create the file /etc/pam.d/kde with the content: #%PAM-1.0 auth include system-auth account include system-auth password include system-auth session include system-auth
I'm using Slackware 12.1 and i'm using kdesvn-build 1.6.2 to compile latest kde svn, but my "Unlock Screen" return password error. This is a pam version error?
I'm not sure if it is a Pam version error, because my distro (Slackware 12.0) does not come with PAM. So I installed the latest version and I did what is in "http://techbase.kde.org/Getting_Started/Build/KDE4/Troubleshooting#Locked_sessions" but I still having the same problem.
*** Bug 171496 has been marked as a duplicate of this bug. ***
*** Bug 172586 has been marked as a duplicate of this bug. ***
*** Bug 175415 has been marked as a duplicate of this bug. ***
Hey, this happens on Solaris as well. Regards, Edward.
Are you still experiencing this issue using KDE 4.2beta1?
Created attachment 29301 [details] my /etc/pam.d/kde
Created attachment 29302 [details] my /etc/pam.d/common-auth
With the latest (as of this post) neon build I am experiencing this issue. I have: chmod 755 $KDEDIR/lib/kde4/libexec/kcheckpass And /etc/pam.d/kde does exist (see previous attachments). I also attached my /etc/pam.d/common-auth
I saw this page: http://techbase.kde.org/Getting_Started/Build/KDE4/Troubleshooting#Locked_sessions But, what about users who do not want to use PAM? I tried the instructions on the page besides installing PAM, and had no luck.
Look at this: bug #166906
I get the same problem with KDE 4.2.0 compiled from the release source tarballs on Slackware 12.2 with Qt 4.4.3. No PAM here either. The permissions on kcheckpass were already correct. Does it need to run with setuid root?
(In reply to comment #15) > I get the same problem with KDE 4.2.0 compiled from the release source tarballs > on Slackware 12.2 with Qt 4.4.3. No PAM here either. The permissions on > kcheckpass were already correct. Does it need to run with setuid root? From kcheckpass README (http://websvn.kde.org/trunk/KDE/kdebase/workspace/kcheckpass/README?view=markup): - No other program in need of user authentication, must be SUID root. --- It's a setup problem - I already experienced that when compiling KDE and not setting kcheckpass SUID root.
*** Bug 265406 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
This bug has been corrected and does not appear in KDE 5.