indicator-messages-service crashed with SIGSEGV in menuproxy_build_cb()

[Brian K. Mangum]

I just had closed Gwibber after setting it not to automatically start at login.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-messages 0.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Fri Mar 2 09:12:24 2012
ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb771023b: mov 0x18(%esi),%eax
 PC (0xb771023b) 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-messages
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: indicator-messages-service crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 menuproxy_build_cb (object=0x95fc620, res=0x960aea8, user_data=0x9602930) at /build/buildd/libdbusmenu-0.5.92/./libdbusmenu-glib/client.c:1069
 g_simple_async_result_complete (simple=0x960aea8) at /build/buildd/glib2.0-2.31.18/./gio/gsimpleasyncresult.c:744
 complete_in_idle_cb (data=0x960aea8) at /build/buildd/glib2.0-2.31.18/./gio/gsimpleasyncresult.c:756
 g_idle_dispatch (source=0x960de10, callback=0xb760ad60 <complete_in_idle_cb>, user_data=0x960aea8) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:4629
 g_main_dispatch (context=0x95ad050) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:2510

[Bilal Akhtar (bilalakhtar)]

Seems like Gwibber actually caused this one.

[Charles Kerr (charlesk)]

In 0.5.92-0ubuntu1, libdbusmenu-glib/client.c:1069 is the first line in this paragraph:

> if (priv->menuproxy_cancel != NULL) {
> g_object_unref(priv->menuproxy_cancel);
> priv->menuproxy_cancel = NULL;
> }

Which makes me think "priv" is corrupt... but we know it's not NULL because the
previous few lines are:

> /* If this wasn't cancelled, we should be good */
> DbusmenuClient * client = DBUSMENU_CLIENT(user_data);
> /* But let's check */
> g_return_if_fail(client != NULL);
> DbusmenuClientPrivate * priv = DBUSMENU_CLIENT_GET_PRIVATE(client);
> g_return_if_fail(priv != NULL);

All those safeguards smell like someone else has tried to track down a crash in this section of code before...

[Charles Kerr (charlesk)]

Aha, found it. I knew with that much smoke there would be something else lurking around in Launchpad... :)

This is a duplicate of Bug #953562 which has already been handled and fixed by desrt