nautilus crashed with SIGSEGV in exit()

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

Bug Description

...

ProblemType: Crash
Architecture: i386
Date: Wed Nov 4 07:16:21 2009
Disassembly: 0x11f9ad0: No se puede acceder a la memoria en la dirección 0x11f9ad0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x11f9ad0: No se puede acceder a la memoria en la dirección 0x11f9ad0
 PC (0x011f9ad0) not located in a known VMA region (needed executable region)!
 source "0x11f9ad0" (0x011f9ad0) not located in a known VMA region (needed readable region)!
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 exit () from /lib/tls/i686/cmov/libc.so.6
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Tags: ubuntu-unr
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
nassao (nassao) 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=0x8081040 <main>, argc=1,
_start () at ../sysdeps/i386/elf/start.S:119

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
affects: ubuntu → nautilus (Ubuntu)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-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.