udisksd crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
when Ubuntu starts
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: udisks2 1.99.0-4
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 8 17:36:57 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28
Lsusb:
Bus 001 Device 003: ID 0480:a006 Toshiba America Info. Systems, Inc.
Bus 001 Device 004: ID 1516:1213 CompUSA
Bus 002 Device 002: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x42e62d: mov (%rax),%ebp
PC (0x0042e62d) 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 quantal on 2012-09-07 (1 days ago)
UserGroups:
dmi.bios.date: 08/03/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.
dmi.board.name: M4N68T-M-LE-V2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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 #1032744, 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.