nautilus crashed with SIGSEGV in malloc()

[luigi massa]

...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Oct 7 23:13:56 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it:en
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 LC_MESSAGES=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f05716d8ce8: mov 0x8(%r14),%rax
 PC (0x7f05716d8ce8) ok
 source "0x8(%r14)" (0x00090009) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_memdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV in malloc()
UpgradeStatus: Upgraded to oneiric on 2011-10-07 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare

[Apport retracing service (apport)]

StacktraceTop:
 _int_malloc (av=0x7f05719f91c0, bytes=32) at malloc.c:4304
 __GI___libc_malloc (bytes=32) at malloc.c:3660
 g_malloc (n_bytes=32) at /build/buildd/glib2.0-2.30.0/./glib/gmem.c:164
 g_memdup (mem=0x7fff6a4dc140, byte_size=32) at /build/buildd/glib2.0-2.30.0/./glib/gstrfuncs.c:128
 nautilus_directory_call_when_ready_internal (directory=0x29e8740, file=0x2ca8c60, file_attributes=3, wait_for_file_list=0, directory_callback=<optimized out>, file_callback=0x488e00 <load_view_as_menus_callback>, callback_data=0xef7b10) at nautilus-directory-async.c:1347

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Sebastien Bacher (seb128)]

no reply, closing the bug