polkit-gnome-authentication-agent-1 crashed with SIGSEGV in gtk_image_get_icon_name()

[Poul-ejlersen]

Binary package hint: policykit-1-gnome

I was running Update Manager, gave passwd to update, and went for a cup of tea...
When I came back, it had crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: policykit-1-gnome 0.96-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Thu Sep 30 00:50:58 2010
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANG=en_DK.utf8
 SHELL=/bin/bash
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_image_get_icon_name () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_image_set_from_pixbuf () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in gtk_image_get_icon_name()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1503): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1491): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:1491): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (polkit-gnome-authentication-agent-1:2774): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 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 #649572, 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.