lvm2-activation-generator crashed with SIGSEGV

Bug #1629146 reported by David Walter
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash when trying to open file manager

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: lvm2 2.02.160-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 29 16:29:49 2016
ExecutablePath: /lib/systemd/system-generators/lvm2-activation-generator
InstallationDate: Installed on 2014-12-17 (652 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /lib/systemd/system-generators/lvm2-activation-generator /run/systemd/generator /run/systemd/generator.early /run/systemd/generator.late
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fc2cac93856: (bad)
 PC (0x7fc2cac93856) ok
 SP (0x7ffcc364b7f0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: lvm2
Stacktrace:
 #0 0x00007fc2cac93856 in ?? () from /lib/x86_64-linux-gnu/liblvm2app.so.2.2
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffcc364e930
StacktraceTop: ?? () from /lib/x86_64-linux-gnu/liblvm2app.so.2.2
ThreadStacktrace:
 .
 Thread 1 (Thread 0x7fc2cb178880 (LWP 5322)):
 #0 0x00007fc2cac93856 in ?? () from /lib/x86_64-linux-gnu/liblvm2app.so.2.2
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffcc364e930
Title: lvm2-activation-generator crashed with SIGSEGV
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (0 days ago)
UserGroups: pkcs11

Revision history for this message
David Walter (davidwalter0) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1605902, 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.

information type: 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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