mount.crypt SIGSEGV's after resume

Bug #798046 reported by Matthias Gehre
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libpam-mount (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: libpam-mount

After I resumed my thinkpad from suspend2ram, I got a message telling me that mount.crypt has been crashed.
I use pam_mount to mount a LUKS encrypted /home whenever I log in.
After that crash, everything still works as expected.
Please provide me with further directions to debug the problem.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libpam-mount 2.8-1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38.2 x86_64
Architecture: amd64
Date: Thu Jun 16 09:07:26 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=0
ProcEnviron: LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x406ede: mov (%r12),%rdi
 PC (0x00406ede) 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=0x402f90, argc=5, ubp_av=0x7fff3c4525f8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff3c4525e8) at libc-start.c:226
 ?? ()
 ?? ()
Title: mount.crypt crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to natty on 2011-04-14 (62 days ago)
UserGroups:

Revision history for this message
Matthias Gehre (m-gehre) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.