You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Monday, September 19th 2005, 1:38pm

unlock session failed

Am running kde 3.4.2 on gentoo. After I lock the screen using the KMenu->Lock Session icon, am unable to unlock it again. Am getting a dialog asking for my password though. It just shows a message unlocking failed on the same dialog. I do not have any other desktop installed apart from kde. What could be the problem?

TIA,
Vignesh.

2

Thursday, November 10th 2005, 5:45pm

RE: unlock session failed

I am also having a similar problem. I am running KDE 3.4 on SuSE 9.3 PRO.

I leave the computer overnight, and it automatically locks the session. However, no matter hoe many times I type in the correct password, it just says "Unlocking Failed."

Any idea what this is?

spimby

Beginner

Posts: 2

Location: Washington, D.C. (USA)

  • Send private message

3

Wednesday, December 14th 2005, 4:40am

RE: unlock session failed

Same problem. Using KDE 3.4.3 (with Kubuntu 5.10) Screensaver will not unlock with correct password.

Lethe

Beginner

Posts: 41

Location: Pompey, England

Occupation: IT network/sysadmin

  • Send private message

4

Wednesday, December 14th 2005, 7:14am

The permissions on kcheckpass are wrong (I had this problem).

You need to change ownership of kcheckpass to root, and then SUID.

> chown root.root `which kcheckpass`
> chmod 4755 `which kcheckpass`

Then all should work.

Nick

spimby

Beginner

Posts: 2

Location: Washington, D.C. (USA)

  • Send private message

5

Friday, December 16th 2005, 5:34am

RE: unlock session failed

That worked. Thanks. Do you know what the permissions/groups should be for the kcheckpass in the etc/pam.d directory? Should they be the same as the one in the usr/bin (I'm new at this)? Thanks.

This post has been edited 1 times, last edit by "spimby" (Dec 16th 2005, 5:35am)


Lethe

Beginner

Posts: 41

Location: Pompey, England

Occupation: IT network/sysadmin

  • Send private message

6

Friday, December 16th 2005, 6:10pm

RE: unlock session failed

I don't know - I haven't a kcheckpass in pam.d

Here is what the README says from the KDE source:

Quoted


The KCheckPass authentication software:
-----------------------------------------

KCheckPass is KDE's authentication program. It is meant to be
used by any software in need of user authentication, most
notably screensavers.

It enhances security be the following means:

- It's only a small program, which is hopefully simple enough to
allow it to be SUID root. Setting it to SUID root is necessary
on Shadow Password systems.
- No other program in need of user authentication, must be
SUID root.
- It provides a single implementation to check passwords. So one
only must take a closer look at KCheckPass to ensure password
security. It's much easier for programs using KCheckPass to
preserve security.


Technique:
----------
KCheckPass is a simple password checker. Just invoke and
send it the password on stdin.

If the password was accepted, the program exits with 0;
if it was rejected, it exits with 1. Any other exit
code signals an error.


So I guess set it up the same.

Nick