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

[Pedro Villavicencio]

Binary package hint: indicator-application

got this after an upgrade

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-application 0.2.94-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CheckboxSubmission: 4afb8c68a8fa5938a80183a271a939ea
CheckboxSystem: c460f5739f7c8446c3d18c3e0e7c5745
Date: Fri Feb 25 08:33:51 2011
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=es_CL.utf8
 LANGUAGE=es_CL:es:en_GB:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x354037 <g_variant_is_trusted+7>: testb $0x4,0x10(%eax)
 PC (0x00354037) ok
 source "$0x4" ok
 destination "0x10(%eax)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-application
StacktraceTop:
 g_variant_is_trusted (value=0x0) at /build/buildd/glib2.0-2.28.1/./glib/gvariant-core.c:600
 g_variant_builder_add_value (builder=0xbf9a98c0, value=0x0) at /build/buildd/glib2.0-2.28.1/./glib/gvariant.c:3081
 g_variant_valist_new (str=0xbf9a9950, app=0xbf9a996c) at /build/buildd/glib2.0-2.28.1/./glib/gvariant.c:4093
 g_variant_new_va (format_string=0x804e636 ")", endptr=0x0, app=0xbf9a996c) at /build/buildd/glib2.0-2.28.1/./glib/gvariant.c:4248
 g_variant_builder_add (builder=0xbf9a99b8, format_string=0x804e62d "(sisossss)") at /build/buildd/glib2.0-2.28.1/./glib/gvariant.c:4390
Title: indicator-application-service crashed with SIGSEGV in g_variant_is_trusted()
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video

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