nautilus crashed with SIGSEGV

Bug #885482 reported by Gabor Toth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

ubuntu 11.10. trying to close a nautilus window. it does not closes and i forced it to close. thus the report.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Wed Nov 2 23:55:40 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x80cc997: mov 0x60(%edx),%eax
 PC (0x080cc997) ok
 source "0x60(%edx)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x080cc997 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfcf27ec
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (19 days ago)
UserGroups: adm admin audio cdrom dialout dip lpadmin netdev plugdev sambashare scanner vboxusers video

Revision history for this message
Gabor Toth (gabor-me) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

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