nautilus crashed with SIGSEGV

Bug #861220 reported by Tomas Žeimys
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

testing Ubuntu 11.10 beta2

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Sep 28 11:16:25 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x486534: mov 0xa8(%rdi),%rax
 PC (0x00486534) 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 0x0000000000486534 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffba29e018
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tomas Žeimys (zeimys) 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 0x7fffba29e018
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.