This bug was originally filed in Launchpad at https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/661254

Description:

Occurs while opening /usr/bin.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 15 15:27:11 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: nautilus --sm-client-id 1035d9d221c5af2642126043856436690500000028700031 --sm-client-state-file /home/username/.config/session-state/nautilus-1265209165.desktop
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc62fd9756e <IA__g_slice_alloc+750>: callq *0x60(%rax)
 PC (0x7fc62fd9756e) ok
 source "*0x60(%rax)" ok
 destination "(%rsp)" (0x7fff0498dfe0) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 thread_memory_from_self (mem_size=32)
 IA__g_slice_alloc (mem_size=32)
 IA__g_slice_alloc0 (mem_size=10035744)
 IA__g_type_create_instance (type=10822432)
 g_object_constructor (type=10035744,
Title: nautilus crashed with SIGSEGV in thread_memory_from_self()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Full debugging information grabbed by apport and a valgrind log are available at the Launchpad bug report to save duplication.