Crash happened while attempting to run IceWM on Ubuntu Lucid (10.04) amd64. The IceWM toolbar never showed up; the user default $HOME/.icewm directory was removed to be sure. Apport reported a crash with this package (gnome-settings-daemon) as well as with icewm (see Bug #447883 ).
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-settings-daemon 2.30.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-42.95-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-42-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Aug 12 21:19:19 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins
ProcEnviron:
LANG=pt_PT.UTF-8
PATH=(custom, no user)
SHELL=/bin/false
LANGUAGE=pt:pt_PT:pt_BR:en
SegvAnalysis:
Segfault happened at: 0x7f54b403f8de <find_image_offset+46>: movsbl 0x0(%rbp),%eax
PC (0x7f54b403f8de) ok
source "0x0(%rbp)" (0x00000060) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
icon_name_hash (cache=0x238d0b0,
find_image_offset (cache=0x238d0b0,
_gtk_icon_cache_get_icon_flags (cache=0x238d0b0,
theme_dir_get_icon_suffix (
theme_lookup_icon (
Title: gnome-settings-daemon crashed with SIGSEGV in icon_name_hash()
UserGroups:
XsessionErrors:
(polkit-gnome-authentication-agent-1:4695): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:4718): Eel-WARNING **: "unique eel_ref_str" hash table still has 4 elements at quit time (keys above)
(nautilus:4718): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 3 elements at quit time
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 729150, so it 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.