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 that on intrepid, here is some output from messages:
Aug 9 13:57:12 trinity gnome-screensav er-dialog: pam_sm_ authenticate: Called er-dialog: pam_sm_ authenticate: username = [luis] er-dialog: Error attempting to parse .ecryptfsrc file; rc = [-5] er-dialog: Unable to read salt value from user's .ecryptfsrc file; using default er-dialog: Passphrase key already in keyring er-dialog: There is already a key in the user session keyring for the given passphrase.
Aug 9 13:57:12 trinity gnome-screensav
Aug 9 13:57:12 trinity gnome-screensav
Aug 9 13:57:12 trinity gnome-screensav
Aug 9 13:57:12 trinity gnome-screensav
Aug 9 13:57:12 trinity gnome-screensav