nautilus crashed with SIGSEGV in g_object_get()

[Leonardo Corato]

Description: Ubuntu precise (development branch)
Release: 12.04

nautilus:
  Installed: 1:3.3.90-0ubuntu2
  Candidate: 1:3.3.90-0ubuntu2
  Version table:
 *** 1:3.3.90-0ubuntu2 0
        500 http://ubuntu.inode.at/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Opening it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CheckboxSubmission: a1c955fd38d4502805ce6f6dc842fe78
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
CrashCounter: 1
Date: Fri Feb 24 16:15:43 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '1132x792+546+24'
 org.gnome.nautilus.window-state sidebar-width 184
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7ff31072dc33 <g_object_get+99>: mov (%rbx),%rax
 PC (0x7ff31072dc33) ok
 source "(%rbx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_object_get()
UpgradeStatus: Upgraded to precise on 2012-02-20 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Leonardo Corato (leocor)]

.

[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.