nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

[Darío Megías Guerrero]

I couldn't drag and drop 2 files into a folder. A graphical bug appeared: black borders of the files appeared on top of the folder they were supposed to be dropped into.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 14:53:38 2017
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'166'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x5588a6040387 <nautilus_window_slot_get_allow_stop+7>: mov 0x98(%rdi,%rax,1),%eax
 PC (0x5588a6040387) ok
 source "0x98(%rdi,%rax,1)" (0xfffffffffffffe78) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_window_slot_get_allow_stop ()
 nautilus_window_sync_allow_stop ()
 nautilus_files_view_update_toolbar_menus ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus: dropbox 2015.10.28

[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 #1724975, 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.