nautilus crashed with SIGSEGV in exit()

[valveillon]

Binary package hint: nautilus

lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

apt-cache policy nautilus
nautilus:
  Installé : 1:2.28.0-0ubuntu7
  Candidat : 1:2.28.0-0ubuntu7
 Table de version :
 *** 1:2.28.0-0ubuntu7 0

Nautilus crashes few seconds after Gnome desktop comes up, it happens at every new login. No specific action needed for this to happen, it seems linked to the session start itself.
The crash doesn't seem to affect the running session, everything else keeps going.

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: 49c9ebbe2d801c7f95a79a72788645ae
CheckboxSystem: 6e17cbbec40a71c458e82f05ea11424b
CrashCounter: 1
Date: Tue Oct 20 16:08:38 2009
Disassembly: 0x7fc76d0df770: Cannot access memory at address 0x7fc76d0df770
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: fglrx
Package: nautilus 1:2.28.0-0ubuntu7
ProcCmdline: nautilus --sm-client-id 10320d9cd46820fbc4125601875764478900000056760039 --sm-client-state-file /home/username/.config/session-state/nautilus-1256046728.desktop
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fc76d0df770: Cannot access memory at address 0x7fc76d0df770
 PC (0x7fc76d0df770) 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 audio cdrom dialout dip floppy fuse lpadmin netdev plugdev scanner vboxusers video

[Apport retracing service (apport)]

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

[Pedro Villavicencio (pedro)]

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.