nautilus crashed with SIGSEGV in g_closure_invoke()

[fabianbur]

nautilus crashed with SIGSEGV in g_closure_invoke()

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb 14 22:49:20 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'288'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1126x791+115+88'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=es_EC:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_EC.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4ac4a4: mov (%r14),%rax
 PC (0x004ac4a4) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

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 #1544277, 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.