indicator-applet crashed with SIGSEGV in g_str_hash()

Bug #433719 reported by Jeremy Visser
206
This bug affects 41 people
Affects Status Importance Assigned to Milestone
DBus Menu
Fix Released
High
Ted Gould
libdbusmenu (Ubuntu)
Fix Released
High
Ted Gould
Karmic
Fix Released
High
Ted Gould

Bug Description

Binary package hint: indicator-applet

indicator-applet crashes several times a day with this error. I am not adept enough to tell whether this is a duplicate of #433553. There is no -dbg package provided, so it is impossible to provide a backtrace with symbols.

This is a spontaneous error — there is nothing I do to trigger it. I am running the following applications which are registered with the applet:

 * Empathy
 * Evolution (with 1 account and its label starts with the letter N and is 6 chars long if that makes any difference)
 * Gwibber
 * Pidgin

It should also be noted that Gwibber and Pidgin are not running on my system, but they still show up in indicator-applet, which if not a feature, seems to be broken behaviour.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 21 09:38:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/indicator-applet/indicator-applet
NonfreeKernelModules: 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=19
ProcEnviron:
 LANG=en_AU.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x7f2fdd169e60 <g_str_hash>: movsbl (%rdi),%eax
 PC (0x7f2fdd169e60) 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 /usr/lib/libglib-2.0.so.0
 g_hash_table_lookup ()
 dbusmenu_menuitem_property_set ()
 g_hash_table_foreach ()
 ?? () from /usr/lib/libdbusmenu-glib.so.0
Title: indicator-applet crashed with SIGSEGV in g_str_hash()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin audio cdrom dialout disk kqemu kvm libvirtd lpadmin plugdev pulse-access sambashare video

Related branches

Revision history for this message
Jeremy Visser (jeremy-visser) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__g_str_hash (v=0x8b18568b48f08948)
IA__g_hash_table_lookup (hash_table=0x1eee990,
dbusmenu_menuitem_property_set (mi=0x1f24940,
IA__g_hash_table_foreach (hash_table=0x1e78510,
menuitem_get_properties_cb (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in indicator-applet (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 433719] Re: indicator-applet crashed with SIGSEGV in g_str_hash()

  affects dbusmenu
  importance medium
  milestone ubuntu-9.10-beta-freeze
  assign ted
  status triaged

David Barth (dbarth)
Changed in dbusmenu:
assignee: nobody → Ted Gould (ted)
Changed in indicator-applet (Ubuntu):
assignee: nobody → Ted Gould (ted)
David Barth (dbarth)
Changed in dbusmenu:
milestone: ubuntu-9.10-beta-freeze → ubuntu-9.10
Changed in indicator-applet (Ubuntu):
importance: Medium → High
milestone: none → ubuntu-9.10
Changed in dbusmenu:
importance: Medium → High
Revision history for this message
Marcel Miebach (marcel-miebach) wrote :

I followed the debugging and backtrace tutorial: https://wiki.ubuntu.com/DebuggingProgramCrash and https://wiki.ubuntu.com/Backtrace .
I added a backtrace. I hope it will help. There still are some question marks.
I also tried to use valgrind and add a memcheck log but it seems that I cannot use valgrind with an applet. Or I did not start the right file for the applet...

Ted Gould (ted)
Changed in dbusmenu:
status: Triaged → Fix Committed
affects: indicator-applet (Ubuntu Karmic) → libdbusmenu (Ubuntu Karmic)
Changed in dbusmenu:
milestone: ubuntu-9.10 → 0.1.6
Ted Gould (ted)
Changed in dbusmenu:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libdbusmenu - 0.1.6-0ubuntu1

---------------
libdbusmenu (0.1.6-0ubuntu1) karmic; urgency=low

  * Upstream release 0.1.6 (LP: #442822)
    * Managing the life-cycle of the GTK Menu item better to
      ensure that it is positioned correctly and dies
      appropriately. (LP: #430904) and (LP: #419953)
    * Checking returned properties to ensure that there wasn't
      DBus errors. (LP: #433719)

 -- Ted Gould <email address hidden> Fri, 02 Oct 2009 17:00:45 -0500

Changed in libdbusmenu (Ubuntu Karmic):
status: New → Fix Released
Revision history for this message
ridgerunner7 (ridgerunner7) wrote :

Verified fixed. I cannot repro the crash any more.

Changed in dbusmenu:
status: Fix Released → In Progress
Ted Gould (ted)
Changed in dbusmenu:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.