nautilus crashed with SIGSEGV

Bug #940543 reported by Arenas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

?

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Feb 24 19:54:08 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x486c94: mov 0xa8(%rdi),%rax
 PC (0x00486c94) ok
 source "0xa8(%rdi)" (0x000000a8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x0000000000486c94 in ?? ()
 No symbol table info available.
 No se puede acceder a la memoria en la dirección 0x7fffa0859798
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare saned scanner tape video
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2011-12-10T09:49:02.656865

Revision history for this message
Arenas (arenas-f) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:646
         __PRETTY_FUNCTION__ = "nautilus_window_slot_get_current_uri"
 Cannot access memory at address 0x7fffa0859798
StacktraceTop: nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:646

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.