mount.crypt crashed with SIGSEGV in __libc_start_main()

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

Bug Description

Crashing very often when resuming from suspend. My /home is mounted by LUKS using pam-mount.
This also happened with natty.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libpam-mount 2.10-2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 2 11:33:01 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: 0x7fe20bfac70e: mov (%r12),%rdi
 PC (0x7fe20bfac70e) 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 () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: mount.crypt crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (0 days ago)
UserGroups:

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

Revision history for this message
Matthias Gehre (m-gehre) wrote :
visibility: private → public
Revision history for this message
Matthias Gehre (m-gehre) wrote :

Some more information: Although the mount.crypt crashes on resume, the /home partition is
usuable and beside from the notification about the crash, I do not encounter any problems.
What can I do to help debugging this?

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.

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.