indicator-application-service crashed with SIGSEGV in g_object_unref()

[Jaromir Obr]

Binary package hint: indicator-application

I've just updated OS (latest updates) and restarted OS (due to new kernel). This crash occurred after login to Gnome.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-application 0.2.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CheckboxSubmission: ca8cd8511cd050bd957f6b0d37298435
CheckboxSystem: 5202e7ee197af4942baf4f50cf4120c6
Date: Tue Nov 23 20:39:16 2010
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4041b5: cmpb $0x0,(%rbx)
 PC (0x004041b5) ok
 source "$0x0" ok
 destination "(%rbx)" (0x726f273d7265646e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-application
StacktraceTop:
 ?? ()
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
Title: indicator-application-service crashed with SIGSEGV in g_object_unref()
UserGroups: adm admin cdrom dialout kqemu kvm libvirtd lpadmin netdev plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1681): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (gnome-settings-daemon:1681): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (polkit-gnome-authentication-agent-1:1712): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-settings-daemon:1681): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' 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 #637202, 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.