Comment 16 for bug 181065

I used to see this on Hardy. I moved to Intrepid a few months back and wasn't seeing this bug until this week.

Interestingly, this always happens when I enter a *wrong* password once at the gnome-screensaver password prompt:
- Lock screen (settings: blank screen, lock when screensaver active).
- Enter wrong password.
- It comes back with the password prompt with a message that the password was incorrect.
- I enter the password again (doesn't matter if its correct/wrong).
- Boom - it hangs there with the 'Checking' message.

Switching to the terminal shows gnome-screensaver using 100% cpu. I've previously just killed gnome-screensaver and moved on, though it looks like it recovers after a long time.

This happens all the time - the magic is to enter a wrong password once/twice at the password prompt.
I'm on Intrepid with latest updates. T61p with nVidia Quadro 570M GPU - 180.29 drivers.

Update: Looking at the logs, I might have found *where* the problem is. The relevant part of auth.log:

Mar 11 18:00:09 xyz-tp unix_chkpwd[8968]: password check failed for user (naveen)
Mar 11 18:00:09 xyz-tp gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=naveen
Mar 11 18:00:10 xyz-tp gnome-screensaver-dialog: gkr-pam: unlocked 'login' keyring
Mar 11 18:00:14 xyz-tp unix_chkpwd[8972]: password check failed for user (naveen)
Mar 11 18:00:14 xyz-tp gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=naveen
Mar 11 18:00:14 xyz-tp gnome-screensaver-dialog: gkr-pam: unlocked 'login' keyring
Mar 11 18:00:20 xyz-tp unix_chkpwd[8976]: password check failed for user (naveen)
Mar 11 18:00:20 xyz-tp gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=naveen
Mar 11 18:08:53 xyz-tp login[8880]: pam_sm_authenticate: Called
Mar 11 18:08:53 xyz-tp login[8880]: pam_sm_authenticate: username = [naveen]
Mar 11 18:08:53 xyz-tp login[8880]: Error attempting to parse .ecryptfsrc file; rc = [-5]
Mar 11 18:08:53 xyz-tp login[8880]: Unable to read salt value from user's .ecryptfsrc file; using default
Mar 11 18:08:53 xyz-tp login[9007]: Error attempting to open [/home/naveen/.ecryptfs/wrapped-passphrase] for reading
Mar 11 18:08:53 xyz-tp login[9007]: Error attempting to unwrap passphrase from file [/home/naveen/.ecryptfs/wrapped-passphrase]; rc = [-5]
Mar 11 18:08:54 xyz-tp login[9007]: Error adding passphrase key token to user session keyring; rc = [-5]
Mar 11 18:08:54 xyz-tp login[8880]: pam_unix(login:session): session opened for user naveen by naveen(uid=0)
Mar 11 18:10:40 xyz-tp login[8880]: pam_unix(login:session): session closed for user naveen
Mar 11 18:10:49 xyz-tp gnome-screensaver-dialog: gkr-pam: unlocked 'login' keyring

In this case, I entered wrong password thrice - the first two times, gnome-screensaver quickly came back with the prompt. The third time, it hung with the 'Checking' message. If we look at the logs above, we can see three log messages associated with each attempt: a "unix_chkpwd" message, a "gnome-screensaver-dialog: pam_unix" message and a "gnome-screensaver-dialog: gkr-pam" message. We can see that with the third attempt (when the dialog box was hung), the third message (unlocking login keyring) is *not* logged rightaway. It takes more than 10 min for that message to appear. The other login messages at 18:08:53-54 are when I logged in at a terminal and I don't think they are related to this problem.

Other seemingly related bugs:
Bug 183486: gnome-screensaver locks up randomly when unlocking screen
Bug 314545: gnome-screensaver bad password timeout

- Naveen