nautilus crashed with SIGSEGV in gconf_client_get()

[marcobra (Marco Braida)]

Description: Ubuntu oneiric (development branch)
Release: 11.10

nautilus:
  Installato: 1:3.2.0-0ubuntu5
  Candidato: 1:3.2.0-0ubuntu5
  Tabella versione:
 *** 1:3.2.0-0ubuntu5 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

I get this crash changing directory

Thanks

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-open-terminal 0.19-1build1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Oct 6 19:14:39 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcCmdline: nautilus
ProcCwd: /home/simonetta
SegvAnalysis:
 Segfault happened at: 0x35b3f99 <gconf_client_get+57>: cmp %eax,(%edx)
 PC (0x035b3f99) ok
 source "%eax" ok
 destination "(%edx)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus-open-terminal
StacktraceTop:
 gconf_client_get () from /usr/lib/libgconf-2.so.4
 gconf_client_get_bool () from /usr/lib/libgconf-2.so.4
 nautilus_open_terminal_get_file_items () from /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
 nautilus_menu_provider_get_file_items () from /usr/lib/libnautilus-extension.so.1
 ?? ()
Title: nautilus crashed with SIGSEGV in gconf_client_get()
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (4 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare tape vboxusers video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #868514, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.