Gnome Screensaver doesn't unlock if ecryptfs is set in pam

I can confirm that on intrepid, here is some output from messages:

Aug 9 13:57:12 trinity gnome-screensaver-dialog: pam_sm_authenticate: Called
Aug 9 13:57:12 trinity gnome-screensaver-dialog: pam_sm_authenticate: username = [luis]
Aug 9 13:57:12 trinity gnome-screensaver-dialog: Error attempting to parse .ecryptfsrc file; rc = [-5]
Aug 9 13:57:12 trinity gnome-screensaver-dialog: Unable to read salt value from user's .ecryptfsrc file; using default
Aug 9 13:57:12 trinity gnome-screensaver-dialog: Passphrase key already in keyring
Aug 9 13:57:12 trinity gnome-screensaver-dialog: There is already a key in the user session keyring for the given passphrase.

I can confirm the issue with Intrepid as well.

I can confirm the bug, and I'm working on it.

:-Dustin

Patch attached, requesting sponsorship.

I have tested this fix, and it works. I'm sending back upstream as well.

:-Dustin

This bug was fixed in the package ecryptfs-utils - 53-1ubuntu3

---------------
ecryptfs-utils (53-1ubuntu3) intrepid; urgency=low

  * debian/patches/00list: add 15-pam_ecryptfs-auth_fork_exit.dpatch.
  * debian/patches/15-pam_ecryptfs-auth_fork_exit.dpatch: fix broken
    exit condition causing screensaver unlocking to fail (LP: #255795).

 -- Dustin Kirkland <email address hidden> Mon, 11 Aug 2008 13:50:59 -0500

I have the same problem with hardy (after resuming computer)

Aug 17 06:59:43 desire gnome-power-manager: (milamber) Resuming computer
Aug 17 07:01:06 desire gnome-screensaver-dialog: pam_sm_authenticate: Called
Aug 17 07:01:06 desire gnome-screensaver-dialog: pam_sm_authenticate: username = [milamber]
Aug 17 07:01:06 desire gnome-screensaver-dialog: Error attempting to parse .ecryptfsrc file; rc = [-5]
Aug 17 07:01:06 desire gnome-screensaver-dialog: Unable to read salt value from user's .ecryptfsrc file; using default
Aug 17 07:01:06 desire gnome-screensaver-dialog: Passphrase key already in keyring
Aug 17 07:01:06 desire gnome-screensaver-dialog: There is already a key in the user session keyring for the given passphrase.

and always whem I use sudo :

Aug 17 07:19:16 desire sudo: pam_sm_authenticate: Called
Aug 17 07:19:16 desire sudo: pam_sm_authenticate: username = [milamber]
Aug 17 07:19:16 desire sudo: Error attempting to parse .ecryptfsrc file; rc = [-5]
Aug 17 07:19:16 desire sudo: Unable to read salt value from user's .ecryptfsrc file; using default
Aug 17 07:19:16 desire sudo: Passphrase key already in keyring
Aug 17 07:19:16 desire sudo: There is already a key in the user session keyring for the given passphrase.

Milamber

On Sun, Aug 17, 2008 at 1:37 AM, MilamberSpace
<email address hidden> wrote:
> I have the same problem with hardy (after resuming computer)

eCryptfs integration in Ubuntu Hardy is minimal, at best.

We have made tremendous strides with eCryptfs and an encrypted private
directory in Intrepid. For this reason, eCryptfs is recommend for
Intrepid and beyond.

:-Dustin