Bug 157338

Summary:	kdesktop_lock refuses to unlock, even with correct password ("Unlocking failed" error message)
Product:	[Unmaintained] kdesktop	Reporter:	Vincent Rubiolo <vincent.rubiolo>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	CLOSED WORKSFORME
Severity:	normal	CC:	finex
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vincent Rubiolo 2008-02-07 14:34:41 UTC

Version:            (using KDE 3.5.8)
Installed from:    Compiled From Sources
Compiler:          gcc-3.4.6 Not sure. I used konstruct and have my local gcc-4.1.2 in my PATH but the config.log seems to say it picked up the 3.4.6 version (system-wide installation from the distro)
OS:                Linux

It is impossible to unlock the desktop when locked by KDE (K menu->Lock session). I have tried several times with a password I know is correct and it always respond with 'Unlocking failed'. When the same password is used on a console login or via GDM, it works fine. The only way I currently have is to log in via the console and kill the kdesktop_lock process.

This is kde-3.5.8 which I built using konstruct (I had the same issue w/ 3.5.7 as well, also built w/ konstruct). I am opening a new bug report because I think the situation differs from the other, seemingly related bugs (#91307, #126728 and #117227) : 
+ there is no message telling that I have to manually kill kdesktop_lock (i.e cantCheck() procedure never called).
+ I have built using konstruct and I am running locally in my own account (this rules out the /etc/pamd/kscreensaver and suid on kcheckpass stuff)

When I launch kdesktop_lock on the command line, I get the same behavior and the following output :
[14:13] vrubiolo@huelgoat ~/InstalledProgs/KDE-3.5.8/bin $ ./kdesktop_lock --forcelock
kdesktop_lock: app 0 0 false 0 0
kdecore (KConfigSkeleton): Creating KConfigSkeleton (0x8fb0788)
kdecore (KConfigSkeleton): KConfigSkeleton::readConfig()
kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-vrubiolo/ksycoca
kdesktop: relPath=System/ScreenSavers/
kdesktop: mForbidden: false
kdesktop: Saver window Id: 20971534
kdesktop: Starting hack: /folk/vrubiolo/InstalledProgs/KDE-3.5.8/bin/kblankscrn.kss
kdesktop: GreeterPlugin classic (classic, Username + password (classic)) loaded
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x140000e
WARNING: DCOPReply<>: cast to 'QStringList' error
WARNING: DCOPReply<>: cast to 'QString' error
Authentication failure
kdesktop: LockProcess: stopping saver

Could you advise on how I can help you pinpoint the issue (I still have my konstruct setup and I am willing to try patches/rebuilds, etc)?

Thanks for your help,

Vincent

PS: this is RHEL WS4 w/ pam-0.77-66.23

Comment 1 Vincent Rubiolo 2008-02-22 16:36:39 UTC

Hello,

Are there any updates here?

Thanks for your help.

Comment 2 Vincent Rubiolo 2008-03-10 14:15:16 UTC

After many investigations, I have finally found that it was PAM which caused the issue :
+ my KDE installation (built with konstruct and located on my home account) had been built on a RHEL3 machine but was being executed on a RHEL4 machine.

+ the PAM service on RHEL3 was 'kde' (as shown in the config.log); an /etc/pam.d/kde file was present on the machine as well. On RHEL4, this file is not present any more and has been replaced by /etc/pam.d/kcheckpass.

+ as soon as I added back the kde file in /etc/pam.d (and renamed the kcheckpass one), things started working again.

It thus seems like a configuration issue, which is why I am closing this bug. However, it might have been desirable to have more information on the failure. I will see to open a new bug report if I can find this is possible.

Comment 3 FiNeX 2009-01-02 20:35:02 UTC

Bug closed. Kdesktop is no more mantained.