nautilus crashed with SIGSEGV in g_type_check_instance()

[Jean-Baptiste Lallement]

Crashes during autopilot tests

TEST CASE:
1. Login to a guest session
2. In a terminal run:
    $ autopilot run -v unity

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.6.3-0ubuntu17
ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
Uname: Linux 3.9.0-4-generic x86_64
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
Date: Mon Jun 10 15:53:06 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1157x646+49+24'"
InstallationDate: Installed on 2012-10-25 (227 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcCwd: /tmp/guest-kIWwnO
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5873b477b9 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f5873b477b9) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) 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_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_object_run_dispose () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to saucy on 2012-12-02 (189 days ago)
UserGroups:

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