nautilus crashed with SIGSEGV in exit()

Bug #414366 reported by vince
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I just start my system and i have this bug

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

apt-cache policy nautilus
nautilus:
  Installé : 1:2.27.4-0ubuntu6
  Candidat : 1:2.27.4-0ubuntu6
 Table de version :
 *** 1:2.27.4-0ubuntu6 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 16 08:09:56 2009
Disassembly: 0x7f4fb5aec5f0:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia wl
Package: nautilus 1:2.27.4-0ubuntu6
ProcCmdline: nautilus
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x7f4fb5aec5f0:
 PC (0x7f4fb5aec5f0) 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-5-generic x86_64
UserGroups: adm audio cdrom dialout dip fax floppy fuse netdev plugdev sambashare tape video

Revision history for this message
vince (vince06fr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
exit () from /lib/libc.so.6
__libc_start_main () from /lib/libc.so.6
_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 :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will greatly aid us in tracking down your problem and resolving this bug.

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
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.