kde screensaver wont unlock

trscookie · 04-23-2006, 09:48 AM

hello all ive just emerged rss-glx( really slick screen savers ) for my kde desktop the problem is when it locks the screen i cant unlock it, even though i have the correct password, ive tried it a million times i have had a look at other peoples problems and one was to change the permisions on kcheckpass chmod 1711 kcheckpass ive also re-emerged kcheckpass with pam in my /etc/make.conf to no avail. please help the only way i can unlock my desktop is to use ctrl+alt+backspace and re-login at the moment!!

dannystaple · 04-23-2006, 09:54 AM

Hi trs,

Okay, have you checked or looked for a log file that might have something on it? Start maybe with /var/log/messages, and then tail that (maybe from a remote machine logged in with a terminal) and then let it go to screensaver and try the password, that may give you some clues.

Now does this occur only with one of the rss screensavers running, or do you get the same behaviour with the more basic screen savers? What about other glx based screensavers? There might be reasons other than anything to do with permissions as to why it might not work as expected.

Danny

trscookie · 04-23-2006, 10:11 AM

cheers for the speedy reply, it seems to be with all the screensavers

ive checked a few this is the last few lines of my /var/log/messages:

Code:

Apr 23 15:52:49 HAL su[8724]: Successful su for root by cookie
Apr 23 15:52:49 HAL su[8724]: + pts/2 cookie:root
Apr 23 15:52:49 HAL su(pam_unix)[8724]: session opened for user root by (uid=500)
Apr 23 15:55:49 HAL su(pam_unix)[8724]: session closed for user root
Apr 23 16:00:01 HAL cron[8782]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 23 16:00:01 HAL cron[8784]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Apr 23 16:10:01 HAL cron[8968]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 23 16:12:35 HAL unix_chkpwd[9037]: check pass; user unknown
Apr 23 16:12:35 HAL kde(pam_unix)[9036]: authentication failure; logname= uid=500 euid=500 tty=:0 ruser= rhost=  user=cookie
Apr 23 16:12:35 HAL kcheckpass[9036]: Authentication failure for cookie (invoked by uid 500)
Apr 23 16:12:38 HAL unix_chkpwd[9039]: check pass; user unknown
Apr 23 16:12:38 HAL kde(pam_unix)[9038]: authentication failure; logname= uid=500 euid=500 tty=:0 ruser= rhost=  user=cookie
Apr 23 16:12:38 HAL kcheckpass[9038]: Authentication failure for cookie (invoked by uid 500)
Apr 23 16:12:42 HAL kdm[6550]: X server for display :0 terminated unexpectedly
Apr 23 16:12:42 HAL kde(pam_unix)[6554]: session closed for user cookie
Apr 23 16:12:44 HAL [fglrx] Internal AGP support requested, but kernel AGP support active.
Apr 23 16:12:44 HAL [fglrx] Have to use kernel AGP support to avoid conflicts.
Apr 23 16:12:44 HAL [fglrx] AGP detected, AgpState   = 0x1f004a1b (hardware caps of chipset)
Apr 23 16:12:44 HAL agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
Apr 23 16:12:44 HAL agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
Apr 23 16:12:44 HAL agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
Apr 23 16:12:44 HAL [fglrx] AGP enabled,  AgpCommand = 0x1f004312 (selected caps)
Apr 23 16:12:44 HAL [fglrx] free  AGP = 121909248
Apr 23 16:12:44 HAL [fglrx] max   AGP = 121909248
Apr 23 16:12:44 HAL [fglrx] free  LFB = 116387840
Apr 23 16:12:44 HAL [fglrx] max   LFB = 116387840
Apr 23 16:12:44 HAL [fglrx] free  Inv = 0
Apr 23 16:12:44 HAL [fglrx] max   Inv = 0
Apr 23 16:12:44 HAL [fglrx] total Inv = 0
Apr 23 16:12:44 HAL [fglrx] total TIM = 0
Apr 23 16:12:44 HAL [fglrx] total FB  = 0
Apr 23 16:12:44 HAL [fglrx] total AGP = 32768
Apr 23 16:12:51 HAL kde(pam_unix)[9056]: session opened for user cookie by (uid=0)
Apr 23 16:13:05 HAL (cookie-6702): SIGHUP received, reloading all databases
Apr 23 16:13:06 HAL (cookie-6702): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Apr 23 16:13:06 HAL (cookie-6702): Resolved address "xml:readwrite:/home/cookie/.gconf" to a writable configuration source at position 1
Apr 23 16:13:06 HAL (cookie-6702): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Apr 23 16:14:38 HAL su[9234]: Successful su for root by cookie
Apr 23 16:14:38 HAL su[9234]: + pts/1 cookie:root
Apr 23 16:14:38 HAL su(pam_unix)[9234]: session opened for user root by (uid=500)

could it be something to do with

Code:

Apr 23 16:12:38 HAL unix_chkpwd[9039]: check pass; user unknown

?

trscookie · 04-23-2006, 01:55 PM

ok right ive logged on as root and root can lock and unlock the screensaver but users cant but ive run chmod 4755 kcheckpass
any ideas??
please help.

trscookie · 04-24-2006, 03:29 AM

ok this is what i get in /var/log/messages if i try to run:

Code:

cookie@HAL ~ $ /usr/kde/3.4/bin/kcheckpass
Password:
Authentication failure

Code:

Apr 24 09:32:46 HAL unix_chkpwd[6822]: check pass; user unknown
Apr 24 09:32:46 HAL kde(pam_unix)[6821]: authentication failure; logname= uid=500 euid=500 tty=/dev/pts/1 ruser= rhost=  user=cookie
Apr 24 09:32:46 HAL kcheckpass[6821]: Authentication failure for cookie (invoked by uid 500)

dannystaple · 04-24-2006, 05:38 PM

Okay - what gets me here is the "user unknown". Is there some wierdness with your /etc/passwd file? Maybe it is not readable for your user "cookie", in which case the app wont be able to check user names. Generally - this file now does not actually store the password itself which is in shadow, but does list all the users on the system.

So could you have a look at the output of 'ls -l /etc/passwd' and say what you have.

Danny

trscookie · 04-24-2006, 05:52 PM

the output for ls -l /etc/passwd and shadow

Code:

-rw-r--r-- 1 root root 1991 Apr 23 21:26 /etc/passwd
-rw------- 1 root root 1184 Apr 23 21:26 /etc/shadow

inside /etc/shadow

Code:

cookie:x:500:100:trscookiek,,,oxford:/home/cookie:/bin/bash

????????