nautilus crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I had totem open and folder open to my usb-stick. Then crash.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: totem 3.18.1-1ubuntu4
ProcVersionSign
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 24 14:31:49 2016
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2016-03-01 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7fc9d0c16913: mov (%rcx),%rdi
PC (0x7fc9d0c16913) ok
source "(%rcx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo vboxusers
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 #1433984, 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.