nautilus crashed with SIGSEGV

Bug #899072 reported by Bibin George
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

its happed when booting from live usb of ubuntu 11.10.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CasperVersion: 1.287.1
Date: Fri Dec 2 01:52:22 2011
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80cc9a7: mov 0x60(%edx),%eax
 PC (0x080cc9a7) 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 0x080cc9a7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf8369cc
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:15551): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
 (canberra-gtk-play:15552): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
 (unity-window-decorator:15600): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
 (applet.py:15683): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
 (firefox:15864): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

Revision history for this message
Bibin George (bibingv) 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 0xbf8369d0
 ) at nautilus-window-slot.c:646
         __PRETTY_FUNCTION__ = "nautilus_window_slot_get_current_uri"
 Cannot access memory at address 0xbf8369cc
StacktraceTop: nautilus_window_slot_get_current_uri (slot=Cannot access memory at address 0xbf8369d0

affects: ubuntu → nautilus (Ubuntu)
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.