Crash report cannot be processed, but the system is up to date.

Bug #860819 reported by Dominik Holler
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Apport
New
Undecided
Unassigned
libpam-mount (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

on ac connect

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libpam-mount 2.10-2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Sep 27 20:59:15 2011
ExecutablePath: /sbin/mount.crypt
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /sbin/mount.crypt /dev/sda7 /home -o rw,remount,commit=0
ProcEnviron: LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x7cb224: mov 0x0(%ebp),%eax
 PC (0x007cb224) ok
 source "0x0(%ebp)" (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:

mtime.conffile..etc.security.pam.mount.conf.xml: 2011-09-04T21:29:31.853441

Revision history for this message
Dominik Holler (dominik-holler) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x7c5e00, argc=5, ubp_av=0xbfa0b504, init=0x7cb370, fini=0x7cb3d0, rtld_fini=0x3ddbc0, stack_end=0xbfa0b4fc) at libc-start.c:226
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libpam-mount (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libslang2: package version 2.2.4-2ubuntu1 dbgsym version 2.2.2-4ubuntu2
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for procps: package version 1:3.2.8-10ubuntu5 dbgsym version 1:3.2.8-10ubuntu3
libglib2.0-0 version 2.29.92-0ubuntu1 required, but 2.30.0-0ubuntu2 is available
outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1
outdated debug symbol package for libnih-dbus1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for libpam-mount: package version 2.10-2 dbgsym version 2.8-1
outdated debug symbol package for libnih1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for dpkg: package version 1.16.0.3ubuntu3 dbgsym version 1.16.0~ubuntu7.1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu1 dbgsym version 3.12-1ubuntu6

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Dominik Holler (dominik-holler) wrote : Re: mount.crypt crashed with SIGSEGV in __libc_start_main()

Crash report cannot be processed, but the system is up to date.

Changed in libpam-mount (Ubuntu):
status: Invalid → New
visibility: private → public
summary: - mount.crypt crashed with SIGSEGV in __libc_start_main()
+ Crash report cannot be processed, but the system is up to date.
Revision history for this message
Dominik Holler (dominik-holler) wrote :

see also #846292 #847181 #849438 #852191 #853469 #854237 #855798 #857713 #859138 #859153

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libpam-mount (Ubuntu):
status: New → Confirmed
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.