udisksd crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
udisksd crashed with SIGSEGV in ffi_call_unix64()
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: udisks2 2.1.0-4
ProcVersionSign
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CustomUdevRuleF
Date: Fri Oct 11 20:03:30 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-07-15 (88 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MachineType: Acer Aspire V3-771
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x4348a5: mov (%rax),%ebp
PC (0x004348a5) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ebp" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
?? ()
?? ()
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
Title: udisksd crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to saucy on 2013-08-12 (59 days ago)
UserGroups:
dmi.bios.date: 04/19/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.
dmi.board.name: VA70_HC
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: Aspire V3-771
dmi.product.
dmi.sys.vendor: Acer
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 #1236510, 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.