mount.crypt crashed with SIGSEGV in __libc_start_main()

[Matthias Gehre]

After _every_ resume from suspend, apport tells me that mount.crypt has crashed. I have my /home encrypted with LUKS and mounted automatically by pam_mount. Beside the message that mount.crypt has crashed, nothing else seems to be wrong.
Especially /home can be accessed like usual.

What can I do to help debugging this?

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libpam-mount 2.10-2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 7 09:40:17 2011
ExecutablePath: /sbin/mount.crypt
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /sbin/mount.crypt /dev/sda7 /home -o rw,remount,commit=600
ProcEnviron: LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x7fd299abd70e: mov (%r12),%rdi
 PC (0x7fd299abd70e) ok
 source "(%r12)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libpam-mount
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x7fd299ab8ba0, argc=5, ubp_av=0x7fff3412d0f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3412d0e8) at libc-start.c:226
 ?? ()
 ?? ()
Title: mount.crypt crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (4 days ago)
UserGroups:

modified.conffile..etc.security.pam.mount.conf.xml: [modified]
mtime.conffile..etc.security.pam.mount.conf.xml: 2011-04-07T02:56:38.101699

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #735587, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.