nautilus crashed with SIGSEGV in g_object_get()

[tr33m4n]

Not too sure what happened here, can't re-create as I don't know what triggered the crash

Description: Ubuntu precise (development branch)
Release: 12.04
nautilus:
  Installed: 1:3.3.5-0ubuntu3
  Candidate: 1:3.3.5-0ubuntu3
  Version table:
 *** 1:3.3.5-0ubuntu3 0
        500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Feb 20 16:11:16 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '800x550+326+191'
 org.gnome.nautilus.window-state start-with-status-bar true
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6c8d9e <g_object_get+30>: mov (%esi),%eax
 PC (0x006c8d9e) ok
 source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_get () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_object_get()
UpgradeStatus: Upgraded to precise on 2012-02-13 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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