nautilus crashed with SIGSEGV in exit()

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

Bug Description

Binary package hint: nautilus

mi usuario , y las funciones de reiniciar, apagar, no arrancaron
cuando inicia el ubunto.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 74efbb146add606170b75999b122a2e8
CheckboxSystem: 4ae27173b679d39cd3eb89bf3037a765
CrashCounter: 1
Date: Sun Sep 27 09:18:59 2009
Disassembly: 0x7aafa20: Cannot access memory at address 0x7aafa20
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: wl
Package: nautilus 1:2.28.0-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
SegvAnalysis:
 Segfault happened at: 0x7aafa20: Cannot access memory at address 0x7aafa20
 PC (0x07aafa20) not located in a known VMA region (needed executable region)!
SegvReason: executing 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
 ?? ()
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
cool_cero (alexredondosk8) 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.