nautilus crashed with SIGSEGV in nautilus_window_slot_get_current_uri()

Bug #801175 reported by Cristian Aravena Romero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Close nautilus and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.0.2-0ubuntu2
Uname: Linux 3.0.0-0300rc4-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jun 23 10:35:37 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=es_ES:en
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 LC_MESSAGES=es_ES.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=0x153f3e0) at nautilus-places-sidebar.c:468
 g_closure_invoke (closure=0x1794560, return_value=0x0, n_param_values=1, param_values=0x7fc62002c6e0, 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=0x7fc6200b4090, emission_return=0x0, instance_and_params=0x7fc62002c6e0) 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=0x7fff4193a838) 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

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.