nautilus crashed with SIGSEGV in *__GI_exit()

Bug #435608 reported by Matt Walker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: nautilus

this happened to me. I have all of the needed debugging packages as well.

ProblemType: Crash
Architecture: i386
Date: Wed Sep 23 16:05:05 2009
Disassembly: 0x7911a20: Cannot access memory at address 0x7911a20
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SegvAnalysis:
 Segfault happened at: 0x7911a20: Cannot access memory at address 0x7911a20
 PC (0x07911a20) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 *__GI_exit (status=0) at exit.c:100
 __libc_start_main (main=0x8080f40 <main>, argc=1,
 _start () at ../sysdeps/i386/elf/start.S:119
Title: nautilus crashed with SIGSEGV in *__GI_exit()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Matt Walker (matthaeus123) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
*__GI_exit (status=0) at exit.c:100
__libc_start_main (main=0x8080f40 <main>, argc=1,
_start () at ../sysdeps/i386/elf/start.S:119

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
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.