gnome-settings-daemon crashed with SIGSEGV in icon_name_hash()

[Yura Tolstik]

Binary package hint: gnome-settings-daemon

ubuntu 10.10

gnome-settings-daemon:
  Installed: 2.30.2-0ubuntu4

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.30.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic i686
Architecture: i386
CrashCounter: 1
Date: Tue Aug 24 23:29:51 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2174fb <find_image_offset+59>: movsbl (%edx),%eax
 PC (0x002174fb) ok
 source "(%edx)" (0x535f4d57) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 icon_name_hash (cache=<value optimized out>,
 find_image_offset (cache=<value optimized out>,
 _gtk_icon_cache_get_icon_flags (cache=0x8533210,
 theme_dir_get_icon_suffix (dir=0x8532838,
 theme_lookup_icon (icon_theme=<value optimized out>,
Title: gnome-settings-daemon crashed with SIGSEGV in icon_name_hash()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape vboxusers video
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2321): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:2320): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (Do:2320): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

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