nautilus crashed with SIGSEGV

Bug #852618 reported by Ted Ekström
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Well I didnt do so much. Do not know what triggered it! But I have change to a other bar Catio-dock.
Mvh

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.90-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Sep 17 15:59:26 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x810eb0d: mov 0x308(%eax),%eax
 PC (0x0810eb0d) ok
 source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x0810eb0d in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfce5d6c
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-14 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ted Ekström (mindbraker20) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x0810eb0d in nautilus_icon_container_search_entry_flush_timeout (container=Cannot access memory at address 0xbfce5d70
 ) at nautilus-icon-container.c:4946
 No locals.
 Cannot access memory at address 0xbfce5d6c
StacktraceTop: nautilus_icon_container_search_entry_flush_timeout (container=Cannot access memory at address 0xbfce5d70

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.