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
=
On Sun, Aug 17, 2008 at 1:37 AM, MilamberSpace
[EMAIL PROTECTED] 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
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
Patch attached, requesting sponsorship.
I have tested this fix, and it works. I'm sending back upstream as
well.
:-Dustin
** Attachment added: ecryptfs-utils.255795.debdiff
http://launchpadlibrarian.net/16711035/ecryptfs-utils.255795.debdiff
--
Gnome Screensaver doesn't unlock if ecryptfs
I can confirm the issue with Intrepid as well.
--
Gnome Screensaver doesn't unlock if ecryptfs is set in pam
https://bugs.launchpad.net/bugs/255795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm the bug, and I'm working on it.
:-Dustin
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Dustin Kirkland (kirkland)
Status: New = Confirmed
--
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