nautilus crashed with SIGSEGV in gtk_widget_set_sensitive()

[GilgongoJones]

Connect to hidden Samba share with "connect to" UI with incorrect credentials. Try again. Nautilus crashes intermittently.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 17 18:34:20 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2016-01-10 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd5837a3ce4: mov (%rbx),%rsi
 PC (0x7fd5837a3ce4) ok
 source "(%rbx)" (0x0000015d) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_widget_set_sensitive () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in gtk_widget_set_sensitive()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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