indicator-applet crashed with SIGSEGV in g_str_hash()

[Rohan Agrawal]

Binary package hint: indicator-applet

Description: Ubuntu karmic (development branch)
Release: 9.10

indicator-applet:
  Installed: 0.2.0-0ubuntu1
  Candidate: 0.2.0-0ubuntu1
  Version table:
 *** 0.2.0-0ubuntu1 0
        500 http://ubuntu.media.mit.edu karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 6 09:45:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/indicator-applet/indicator-applet
NonfreeKernelModules: openafs nvidia
Package: indicator-applet 0.2.0-0ubuntu1
ProcCmdline: /usr/lib/indicator-applet/indicator-applet --oaf-activate-iid=OAFIID:GNOME_IndicatorApplet_Factory --oaf-ior-fd=26
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x7fa18ef6cc80 <g_str_hash>: movsbl (%rdi),%eax
 PC (0x7fa18ef6cc80) ok
 source "(%rdi)" (0x8b18568b48f08948) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-applet
StacktraceTop:
 g_str_hash () from /lib/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 dbusmenu_menuitem_property_set ()
 g_hash_table_foreach () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libdbusmenu-glib.so.0
Title: indicator-applet crashed with SIGSEGV in g_str_hash()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape vboxusers 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 #442374, 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.