gnome-power-manager crashed with SIGSEGV in icon_name_hash()

[Franck]

Binary package hint: gnome-power-manager

gnome-power-manager crashed with SIGSEGV in icon_name_hash()

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CrashCounter: 1
Date: Thu Apr 1 21:40:56 2010
ExecutablePath: /usr/bin/gnome-power-manager
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x108f00b <find_image_offset+59>: movsbl (%edx),%eax
 PC (0x0108f00b) ok
 source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 icon_name_hash (cache=<value optimized out>,
 find_image_offset (cache=<value optimized out>,
 _gtk_icon_cache_get_icon_flags (cache=0x96af918,
 theme_dir_get_icon_suffix (dir=<value optimized out>,
 theme_lookup_icon (icon_theme=<value optimized out>,
Title: gnome-power-manager crashed with SIGSEGV in icon_name_hash()
UserGroups: audio cdrom dialout dip floppy plugdev scanner
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1542): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (trackerd:1556): Tracker-CRITICAL **: Could not initialize the HAL context, no error, is hald running?
 (gnome-terminal:1953): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

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