In our patched version of glib2.0-2.31.18, that crash occurs on the
first line of g_dbus_proxy_call_internal():
> g_return_if_fail (G_IS_DBUS_PROXY (proxy));
so it looks like we're passing a broken pointer in as the proxy argument
there. Following the trace back one step, this proxy pointer is the same
one that libindicate/listener.c's indicator_listener_display() passes to
g_dbus_proxy_call(). So it looks like the IndicateListenerServer.proxy
pointer passed into that function is bad.
My guess is that priv->server.proxy isn't getting updated when the proxy
is destroyed. proxy_destroyed() updates its "priv->proxies" array but
does nothing for "priv->server.proxy".
** Also affects: libindicate
Importance: Undecided
Status: New
** Changed in: libindicate
Status: New => Confirmed
** Changed in: indicator-messages
Status: Confirmed => Invalid
** Changed in: libindicate
Importance: Undecided => Medium
** Changed in: libindicate
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944900
Title:
indicator-messages-service crashed with SIGSEGV in
g_dbus_proxy_call_internal()
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-messages/+bug/944900/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
