mount.crypt crashed with SIGSEGV in __libc_start_main()

Bug #746767 reported by u-foka
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

I get this apport prompt every time power manager tryes to remount my encrypted home partition

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libpam-mount 2.8-1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Thu Mar 31 23:42:46 2011
ExecutablePath: /sbin/mount.crypt
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110327)
LocalLibraries: /usr/local/lib/libkeepalive.so
ProcCmdline: /sbin/mount.crypt /dev/sda6 /home/u-foka -o rw,remount,commit=600,commit=0
ProcEnviron: LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x804e759: mov (%esi),%eax
 PC (0x0804e759) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libpam-mount
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: mount.crypt crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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-i386-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.