After upgrading from pam_mount 1.26 to version 1.31 (and the corresponding libhx version 3.0.1), no mounting is performed any longer by pam_mount. Downgrading to 1.26 and libhx version 2.7 results in mounting being performed again. This is not connected to the udev version (no difference between 124 and 141) and is not restricted to encrypted mounts - so not related to bug 262475. Seen on two amd64 systems with 2008.0.
Created attachment 204245 [details] syslog of 1.26 (working)
Created attachment 204247 [details] syslog of 1.31 (failed)
Created attachment 204249 [details] emerge --info output
When diffing working.out and failed.out, it shows that pmvarrun is only invoked in the failed log, and no sanity check or mount attempt is performed there...
It might be worth mentioning that I'm only having user-specific volumes to mount. Nothing systemwide...
Upstream says this is now fixed, can you please try with 1.32?
I've tried 1.32, and my crypt filesystem gets mounted, so the bug is solved. I get quite confusing output though when logging in (without debug turned off): pam_mount(mount.c:64): Errors from underlying mount program: pam_mount(mount.c:68): Command successful. After a glance in the source, this looks to me more like a bug in libhx than in pam_mount, so I'd consider this ticket resolved. Thanks!
Not a real bug, but probably not nice, too. Can you write the pam-mount-author about it? he usually is quite helpful and responsitive.
