nautilus crashed with SIGSEGV

Bug #840774 reported by Olli Kankare
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Nautilus crashed while in the background.
Activating the window showed a non-responsive nautilus window which popped up a crash-report upon closing.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 4 08:08:00 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x486f54: mov 0xa8(%rdi),%rax
 PC (0x00486f54) 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 0x0000000000486f54 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff0420bb38
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Olli Kankare (o.k) 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:648
         __PRETTY_FUNCTION__ = "nautilus_window_slot_get_current_uri"
 Cannot access memory at address 0x7fff0420bb38
StacktraceTop: nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:648

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