hud-service crashed with SIGSEGV in g_simple_async_result_complete()

[esodin]

When opening an attached PDF file (by dobbel-clicking) using Firefox at Outlook web mail a generic message telling me that "Ubuntu has crashed - try to restart". The PC seems to work fine after the message. I am sorry I can not be more specific - I expected a restart and did not note any other specific data.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.92-0ubuntu1
Uname: Linux 3.3.0-030300rc6-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 81b0e7cdf92513516e77e0cf6570c645
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
Date: Wed Mar 14 06:08:52 2012
ExecutablePath: /usr/lib/indicator-appmenu/hud-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/indicator-appmenu/hud-service
SegvAnalysis:
 Segfault happened at: 0x7f0e9d22a1a9: mov 0x30(%rbx),%rdi
 PC (0x7f0e9d22a1a9) ok
 source "0x30(%rbx)" (0xaaaaaaaaaaaaaada) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: hud-service crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to precise on 2012-03-10 (3 days ago)
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 this software better. This particular crash has already been reported and is a duplicate of bug #953562, 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.