| Summary: | kdesktop_lock fails to unlock;"Cannot unlock the session because the authentication system failed to work; you must kill kdesktop_lock (pid xxxx) manually. | ||
|---|---|---|---|
| Product: | [Unmaintained] kdesktop | Reporter: | Peter R. Thorsen Jr. <prt7u> |
| Component: | general | Assignee: | Oswald Buddenhagen <ossi> |
| Status: | CLOSED NOT A BUG | ||
| Severity: | normal | CC: | finex, rdieter |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Peter R. Thorsen Jr.
2006-05-04 13:00:09 UTC
I to have this very same problem Sorry finger trouble. After using Yum to perform updates to my system fedora core 5, i honestly could not say which updates were applied with out looking into it more. i now to am seeing this problem. Glad it aint just me. I too have this bug after installing patches. ......Brian Kaye Added a bunch more patches today some of which were to KDE and the problem seems to have gone away. Did not restart X or anything. Yep the updates i installed today have fixed the lock desktop issue. problem gone. As others have said as of yesterday the updates that I downloaded and installed this morning seemed to have fixed this issue. Thanks, Pete This bug is definitely not resolved in kubuntu edgy (KDE 3.5.5), I first noticed it when I had locked my desktop and it refused to unlock, even though the password I entered was correct. It seems that the commandline kcheckpass is used, and if I run this from a shell, it fails every time, no matter which of my 5 user accounts I use. In /var/log/auth.log I see these lines : Jan 24 21:40:18 localhost kcheckpass: (pam_unix) authentication failure; logname= uid=1000 euid=1000 tty=/dev/pts/2 ruser= rhost= user=joris Jan 24 21:40:18 localhost kcheckpass[9008]: Authentication failure for joris (invoked by uid 1000) Confirmed. I have this problem on kubuntu dapper too. Is there a quick fix for this? Because hibernation and sleep also depends on it. ... and, please: This is confirmed, perhaps worse than normal, too, because you have to crash your system, that is the only way -- crash X, reboot or warever -- your work may be lost, at least what you wanted to return to. As soon you knows this, it is probaly not that bad, but who woulkd expect such a normal feature to be broken? This bug has 40 votes now, this means It is rendered important. 40 is nothing, it's 2 people, but yes, this bug seems grave. However I have no idea about that code; ossi is in the authors for kcheckpass so I hope he has a bit more of an idea about this problem. usually this comes from kcheckpass not being setuid root or setgid shadow. needless to say: works for me. I can vouge the folks using kde-redhat pkgs were (most likely) simply packaging bugs introduced in kdebase-3.5.5-1.5 (released Jan 04), fixed in kdebase-3.5.6-3 (released Jan 22). My bad, sorry. Can't speak for kubuntu folks having similar problems. thx rex. i assume the ubuntu folks are seeing a homologous problem. Bug closed. Kdesktop is no more mantained. |