hud-service crashed with SIGSEGV in g_datalist_id_get_data()

[Spect]

hud-service crashed with SIGSEGV in g_datalist_id_get_data()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
CrashDB: indicator_appmenu
Date: Sun Jul 1 12:09:40 2012
ExecutablePath: /usr/lib/indicator-appmenu/hud-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac (20120425.1)
ProcCmdline: /usr/lib/indicator-appmenu/hud-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=ru_UA:ru
 LANG=ru_UA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0634d832d5 <g_datalist_id_get_data+69>: callq 0x7f0634d75a30 <g_pointer_bit_lock>
 PC (0x7f0634d832d5) ok
 source "0x7f0634d75a30" (0x7f0634d75a30) ok
 destination "(%rsp)" (0x7fff5fc18000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 g_datalist_id_get_data () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.0
ThirdParty: True
Title: hud-service crashed with SIGSEGV in g_datalist_id_get_data()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1013226, 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.