I found that this happened when the mount point was somewhere that the user had permissions to create the directory: in my case it was under /tmp, but somewhere under $HOME would have the same behaviour. The problem is that chown isn't allowed, since you aren't root; then the code tries to make the directory again (this time as root), but fails because it already exists.
A workaround is to mount the directory somewhere where only root has permissions to create directories. For myself I chose to place it under /var/run. When I have a moment I will whip up a patch that makes it remove the directory when the chown fails, and post that here for possible SRUing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/557025 Title: pam_mount.so chown to user when creating directory fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/557025/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
