nautilus crashed with SIGSEGV in g_type_check_instance()

[Cysioland]

1. I create a folder with Ctrl+Shift+N
2. I type in name
3. [ENTER]
4. It hangs
5. Crash

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.14.2-0ubuntu13
Uname: Linux 4.2.5-040205-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Nov 28 20:11:14 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2014-10-14 (410 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=pl_PL
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/usr/bin/fish
SegvAnalysis:
 Segfault happened at: 0x7f6ca3b66e39 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f6ca3b66e39) ok
 source "(%rax)" (0x70616e00676e702e) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_connect_data () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to wily on 2015-10-27 (32 days ago)
UserGroups: adm cdrom dialout dip disk lpadmin mythtv plugdev sambashare sudo vboxusers wireshark

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