nautilus crashed with SIGSEGV in g_str_hash()

[axel]

Binary package hint: nautilus

while opening "search for other programs" nautilus crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Feb 13 03:17:02 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110210)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6cc64c <g_str_hash+12>: movzbl (%ecx),%edx
 PC (0x006cc64c) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_str_hash () from /lib/libglib-2.0.so.0
 ?? ()
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_str_hash()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1397): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (polkit-gnome-authentication-agent-1:1409): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed
 (nautilus:1397): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:9147): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
usr_lib_nautilus: nautilus 1:2.32.2.1-0ubuntu5brasero 2.32.1-0ubuntu1gnome-disk-utility 2.32.1-0ubuntu3nautilus-share 0.7.2-14ubuntu1totem 2.32.0-0ubuntu8file-roller 2.32.1-0ubuntu2nautilus-sendto 2.32.0-0ubuntu1ubuntuone-client-gnome 1.5.4-0ubuntu1evince 2.32.0-0ubuntu9

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