Re: KDE desktop unlock fails due to authentication failure
Le Mon, 25 Aug 2008 13:40:08 +0200, Bruno Voigt a écrit :
> Hi,
> I'm using a daily updated debian/unstable system with KDE desktop. Since
> about 3-4 week I can no longer succesfully unlock the desktop with my
> password after auto-lockup (msg: "unlock failed.."). So after
> auto-lockup I have to switch to a text VT and kill the kdesktop_lock
> process.
>
> Do I have to adjust some config to make it work again? Reboot did not
> help.
> There was a new pam version installed, I don't know if/how it relates to
> the problem, eg. if some manual changes have to be done which were not
> automatically handled..etc..
>
> I've found following message - but cannot figure out what's going wrong:
>
> bruno@host:~$ cat .xsession-errors
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x4e00011
> WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>:
> cast to 'QString' error Authentication failure
>
> TIA,
> Bruno
Hi Bruno,
have a look at the files /etc/shadow and /sbin/unix_chkpwd. The owner
should be "root" for the user, and "shadow" for the group.
Reply to: