nautilus crashed with SIGSEGV in nautilus_window_slot_get_current_uri()

[Cristian Aravena Romero]

Binary package hint: nautilus

Unmount 2 sftp.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.0.2-0ubuntu2
Uname: Linux 3.0.0-0300rc3-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jun 16 21:02:09 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=es_CL:es_ES:en
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x486984 <nautilus_window_slot_get_current_uri+4>: mov 0xb0(%rdi),%rax
 PC (0x00486984) ok
 source "0xb0(%rdi)" (0x000000b0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:655
 update_places (sidebar=0xc08400) at nautilus-places-sidebar.c:468
 g_closure_invoke (closure=0x7fb96c83f950, return_value=0x0, n_param_values=2, param_values=0x7fb96c037030, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0xb6fb60, emission_return=0x0, instance_and_params=0x7fb96c037030) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3256
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=0x7fff8eb94838) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2987
Title: nautilus crashed with SIGSEGV in nautilus_window_slot_get_current_uri()
UpgradeStatus: No upgrade log present (probably fresh install)
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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #797463, 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.