nautilus crashed with SIGSEGV in g_timeout_dispatch()

[Cristian Aravena Romero]

I'm working with nautilus and then appeared a window notification of crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Sat Aug 13 21:54:01 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4c0cbe: mov 0x390(%rax),%rdi
 PC (0x004c0cbe) ok
 source "0x390(%rax)" (0xaaaaaaaaaaaaae3a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_timeout_dispatch (source=0x7f90b82740c0, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:3991
 g_main_dispatch (context=0x1cbcca0) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:2500
 g_main_context_dispatch (context=0x1cbcca0) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:3083
 g_main_context_iterate (context=0x1cbcca0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:3161
Title: nautilus crashed with SIGSEGV in g_timeout_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-08-13 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 nautilus_icon_container_search_entry_flush_timeout (container=0x2089460) at nautilus-icon-container.c:4947
 g_main_loop_run (loop=0x7f90b82740c0) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:3278
 ?? ()
 g_main_loop_run (loop=0x27c1f50) at /build/buildd/glib2.0-2.29.16/./glib/gmain.c:3278
 ?? ()

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 804133, so it 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.