nautilus crashed with SIGSEGV

[epic456]

closing unresponsive windows (mounted ntfs disk)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.90-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 14 03:00:07 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x486804: mov 0xa8(%rdi),%rax
 PC (0x00486804) 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 0x0000000000486804 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff8d278ee8
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-08-28 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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

[Robert Roth (evfool)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.