nautilus crashed with SIGSEGV in exit()

Bug #471497 reported by Géza Búza
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: nautilus

1) Release: 9.10
    Architecture: amd64
2) nautilus Version: 1:2.28.1-0ubuntu1
3) I searched for something with gnome-do Version: 0.8.2+dfsg-1
4) nautilus crashed

ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 00:13:54 2009
Disassembly: 0x7f31bf6a5770: Cannot access memory at address 0x7f31bf6a5770
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: fglrx
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f31bf6a5770: Cannot access memory at address 0x7f31bf6a5770
 PC (0x7f31bf6a5770) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 exit () from /lib/libc.so.6
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Géza Búza (medve) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
*__GI_exit (status=0) at exit.c:78
__libc_start_main (main=<value optimized out>,
_start () at ../sysdeps/x86_64/elf/start.S:113

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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.