nautilus crashed with SIGSEGV in gconf_client_get()

[Mohamed Ghorab]

when i browse any path in my HDD or removable desk

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-open-terminal 0.19-1build1
Uname: Linux 3.1.0-0301rc4-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sun Oct 9 14:50:41 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0xb48bcf99 <gconf_client_get+57>: cmp %eax,(%edx)
 PC (0xb48bcf99) ok
 source "%eax" ok
 destination "(%edx)" (0x00000080) 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-08 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1449): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1449): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (gwibber-service:1602): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

[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 #869856, 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.