telepathy-indicator crashed with signal 5 in g_simple_async_result_complete()

Bug #925829 reported by Sathish Kumar on 2012-02-03
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libindicate
New
High
Charles Kerr
telepathy-indicator (Ubuntu)
Medium
Unassigned

Bug Description

after updatingt alpha 2,telepathy crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-indicator 0.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 3 06:49:54 2012
ExecutablePath: /usr/bin/telepathy-indicator
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120128)
ProcCmdline: telepathy-indicator
Signal: 5
SourcePackage: telepathy-indicator
StacktraceTop:
 ?? () from /usr/lib/libindicate.so.5
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: telepathy-indicator crashed with signal 5 in g_simple_async_result_complete()
UpgradeStatus: Upgraded to precise on 2012-02-03 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Sathish Kumar (sathish-394) wrote :

StacktraceTop:
 bus_connection_cb (obj=<optimized out>, res=<optimized out>, user_data=0x161e820) at /build/buildd/libindicate-0.6.1/./libindicate/server.c:694
 g_simple_async_result_complete (simple=0x16135e0) at /build/buildd/glib2.0-2.31.14/./gio/gsimpleasyncresult.c:744
 complete_in_idle_cb (data=0x16135e0) at /build/buildd/glib2.0-2.31.14/./gio/gsimpleasyncresult.c:756
 g_main_dispatch (context=0x1609350) at /build/buildd/glib2.0-2.31.14/./glib/gmain.c:2510
 g_main_context_dispatch (context=0x1609350) at /build/buildd/glib2.0-2.31.14/./glib/gmain.c:3047

Changed in telepathy-indicator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Bilal Shahid (s9iper1) on 2012-02-29
visibility: private → public
Bilal Shahid (s9iper1) on 2012-02-29
Changed in telepathy-indicator (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
status: New → Triaged
Ken VanDine (ken-vandine) wrote :

This looks like a libindicate bug

affects: telepathy-indicator → libindicate
Changed in libindicate:
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-indicator - 0.2.1-0ubuntu1

---------------
telepathy-indicator (0.2.1-0ubuntu1) precise; urgency=low

  * New upstream release
    - Bugs fixed:
      * shows my own nick name in chat notifications, not the one of the
        peer (LP: #926072)
      * Use IndicateInterests to determine if there are listeners, this will
        prevent crashers if telepathy-indicator gets run in gnome-shell or
        other environments without a messaging indicator (LP: #947590)
      * Only autostart in Unity and GNOME classic
      * SIGSEGV in g_file_get_path() (LP: #910785)
      * crashed with signal 5 in g_simple_async_result_complete() (LP: #925829)
      * SIGSEGV in handle_contacts_pending_add_indicator_cb() (LP: #929002)
 -- Ken VanDine <email address hidden> Thu, 22 Mar 2012 11:06:05 -0400

Changed in telepathy-indicator (Ubuntu):
status: Triaged → Fix Released
Ken VanDine (ken-vandine) wrote :

This shouldn't have been referenced in the telepathy-indicator changelog, it is not fixed yet.

Changed in telepathy-indicator (Ubuntu):
status: Fix Released → New
status: New → Triaged
assignee: Ken VanDine (ken-vandine) → nobody
Olli Ries (ories) on 2012-03-27
Changed in libindicate:
assignee: nobody → Charles Kerr (charlesk)
importance: Low → High
Charles Kerr (charlesk) wrote :

Okay, it's definintely crashing in libindicate. The process is in libindicate/server.c's bus_connection_cb() callback func and calls g_bus_get_finish() to complete making the connection. g_bus_get_finish() returns an error, which bus_connection_cb() tries to log. The crash takes place while logging the error, making me think the error message is corrupt.

The code:

    static void
    bus_connection_cb (GObject * obj, GAsyncResult * res, gpointer user_data)
    {
            GError * error = NULL;

            GDBusConnection * connection = g_bus_get_finish(res, &error);
            if (error != NULL) {
                    g_error("Unable to get session bus: %s", error->message);
                    g_error_free(error);
                    return;
            }

And the relevant parts of the ThreadStacktrace:

#0 g_logv (log_domain=0x7f6e5e523432 "libindicate", log_level=<optimized out>, format=0x7f6e5e5237c6 "Unable to get session bus: %s", args1=0x7fff70a89ac8) at /build/buildd/glib2.0-2.31.14/./glib/gmessages.c:765
        domain = 0x0
        data = <optimized out>
        depth = 0
        log_func = <optimized out>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = <optimized out>
        test_level = <optimized out>
        was_fatal = 0
        was_recursion = 0
        i = <optimized out>
#1 0x00007f6e5d47f062 in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>) at /build/buildd/glib2.0-2.31.14/./glib/gmessages.c:792
        args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fff70a89ba0, reg_save_area = 0x7fff70a89ae0}}
#2 0x00007f6e5e51dd6c in bus_connection_cb (obj=<optimized out>, res=<optimized out>, user_data=0x161e820) at /build/buildd/libindicate-0.6.1/./libindicate/server.c:694
        error = 0x16288b0
        connection = 0x0
        server = <optimized out>
        priv = <optimized out>

Charles Kerr (charlesk) wrote :

See also Bug #852027, that one's in libindicator but has the same pattern.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers