nautilus crashed with SIGSEGV in g_object_get_data()

[luigi massa]

nothings

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 8 22:04:54 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it:en
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 LC_MESSAGES=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa4961be061 <g_object_get_data+33>: cmpq $0x50,(%rax)
 PC (0x7fa4961be061) ok
 source "$0x50" ok
 destination "(%rax)" (0x00000030) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_get_data () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gtk_tree_row_reference_free () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
Title: nautilus crashed with SIGSEGV in g_object_get_data()
UpgradeStatus: Upgraded to oneiric on 2011-10-07 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_object_get_data (object=<optimized out>, key=0x7fa49865de1c "gtk-tree-row-refs") at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:2940
 gtk_tree_row_reference_free (reference=0x2655bb0) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreemodel.c:2415
 garbage_collect_cell_data (data=0x1023c10) at /build/buildd/gtk+3.0-3.2.0/./gtk/a11y/gtktreeviewaccessible.c:2841
 idle_garbage_collect_cell_data (data=0x1023c10) at /build/buildd/gtk+3.0-3.2.0/./gtk/a11y/gtktreeviewaccessible.c:2863
 gdk_threads_dispatch (data=0x264b160) at /build/buildd/gtk+3.0-3.2.0/./gdk/gdk.c:754

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Sebastien Bacher (seb128)]

no reply, closing the bug