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

[Ramiro Queso]

Binary package hint: indicator-application

ubuntu 10.10 beta

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-application 0.2.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
CheckboxSubmission: cc38e5cb3a0b5e5563775f0018e7512b
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Tue Sep 14 08:20:16 2010
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_BO.utf8
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 lpadmin plugdev sambashare

[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.