hud-service crashed with SIGSEGV in g_simple_async_result_complete()

[Lukasz Pozniak]

lukas@mikrus:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
lukas@mikrus:~$ apt-cache policy indicator-appmenu
indicator-appmenu:
  Installed: 0.3.92-0ubuntu2
  Candidate: 0.3.92-0ubuntu2
  Version table:
 *** 0.3.92-0ubuntu2 0
        500 http://pl.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

Crash happens just after logging in

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 10:15:29 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/indicator-appmenu/hud-service
ProcCmdline: /usr/lib/indicator-appmenu/hud-service
SegvAnalysis:
 Segfault happened at: 0x33227b: mov 0x18(%esi),%eax
 PC (0x0033227b) ok
 source "0x18(%esi)" (0xaaaaaac2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-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-14 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers vmware

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