empathy-chat crashed with SIGSEGV in _tp_base_client_handle_channels()

Bug #829861 reported by Cristian Aravena Romero
110
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Telepathy Glib
Won't Fix
Medium
telepathy-glib (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I'm working with empathy and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 19 21:25:33 2011
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/lib/empathy/empathy-chat
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ffd0eb8d477 <_tp_base_client_handle_channels+343>: mov 0x8(%rax),%r8
 PC (0x7ffd0eb8d477) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 _tp_base_client_handle_channels (iface=<optimized out>, account_path=<optimized out>, connection_path=<optimized out>, channels_arr=0x25e0cc0, requests_arr=0x25e0d80, user_action_time=0, handler_info=0x25df5e0, context=0x25e33e0) at base-client.c:2336
 _tp_marshal_VOID__BOXED_BOXED_BOXED_BOXED_UINT64_BOXED_POINTER (closure=0x7fff1a676bd0, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x25b4400, invocation_hint=<optimized out>, marshal_data=<optimized out>) at _gen/signals-marshal.c:452
 invoke_object_method (message=0x25a5f10, connection=0x24ebc40, method=0x7ffd0eee9ca0, object_info=0x7ffd0eee7e00, object=0x25d11b0) at dbus-gobject.c:1744
 object_registration_message (connection=0x24ebc40, message=0x25a5f10, user_data=<optimized out>) at dbus-gobject.c:1968
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: empathy-chat crashed with SIGSEGV in _tp_base_client_handle_channels()
UpgradeStatus: Upgraded to oneiric on 2011-08-19 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
In , Cristian Aravena Romero (caravena) wrote :
Download full text (5.8 KiB)

Open bug in launchpad.net:
https://bugs.launchpad.net/bugs/829861

"I'm working with empathy and crash."

#0 _tp_base_client_handle_channels (iface=<optimized out>, account_path=<optimized out>, connection_path=<optimized out>, channels_arr=0x25e0cc0, requests_arr=0x25e0d80, user_action_time=0, handler_info=0x25df5e0, context=0x25e33e0) at base-client.c:2336
        chan_path = 0x25af200 "/org/freedesktop/Telepathy/Connection/idle/irc/username_40chat_2efreenode_2enet0x100c1b0/MucChannel1"
        chan_props = 0x25df580
        self = 0x25d11b0
        ctx = <optimized out>
        cls = <optimized out>
        error = 0x0
        account = 0x25d87a0
        connection = 0x24d0170
        channels = 0x25e0a60
        requests = 0x0
        i = <optimized out>
        channel = 0x0
        account_features = <optimized out>
        connection_features = <optimized out>
        channel_features = <optimized out>
        __PRETTY_FUNCTION__ = "_tp_base_client_handle_channels"
#1 0x00007ffd0ec5b687 in _tp_marshal_VOID__BOXED_BOXED_BOXED_BOXED_UINT64_BOXED_POINTER (closure=0x7fff1a676bd0, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x25b4400, invocation_hint=<optimized out>, marshal_data=<optimized out>) at _gen/signals-marshal.c:452
        callback = 0x7ffd0ec695b0 <tp_svc_client_handler_handle_channels>
        cc = 0x7fff1a676bd0
        data1 = 0x25d11b0
        data2 = <optimized out>
        __PRETTY_FUNCTION__ = "_tp_marshal_VOID__BOXED_BOXED_BOXED_BOXED_UINT64_BOXED_POINTER"
#2 0x00007ffd0f11d9c2 in invoke_object_method (message=0x25a5f10, connection=0x24ebc40, method=0x7ffd0eee9ca0, object_info=0x7ffd0eee7e00, object=0x25d11b0) at dbus-gobject.c:1744
        had_error = <optimized out>
        value_array = 0x25e0ca0
        result = <optimized out>
        gerror = 0x0
        closure = {ref_count = 0, meta_marshal = 0, n_guards = 0, n_fnotifiers = 0, n_inotifiers = 0, in_inotify = 0, floating = 0, derivative_flag = 0, in_marshal = 0, is_invalid = 0, marshal = 0, data = 0x0, notifiers = 0x0}
        out_param_pos = <optimized out>
        have_retval = 0
        send_reply = <optimized out>
        in_signature = 0x25e07d0 "ooa(oa{sv})aota{sv}"
        out_param_count = <optimized out>
        out_param_gvalue_pos = <optimized out>
        retval_signals_error = 0
        arg_metadata = <optimized out>
        is_async = 1
        out_param_values = 0x0
        return_value = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        out_param_gvalues = 0x0
        reply = 0x0
        retval_is_synthetic = 0
        retval_is_constant = 0
#3 object_registration_message (connection=0x24ebc40, message=0x25a5f10, user_data=<optimized out>) at dbus-gobject.c:1968
        pspec = <optimized out>
        object = 0x25d11b0
        setter = <optimized out>
        getter = <optimized out>
        getall = <optimized out>
        s = <optimized out>
        requested_propname = <optimized out>
        ...

Read more...

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _tp_base_client_handle_channels (iface=<optimized out>, account_path=<optimized out>, connection_path=<optimized out>, channels_arr=0x25e0cc0, requests_arr=0x25e0d80, user_action_time=0, handler_info=0x25df5e0, context=0x25e33e0) at base-client.c:2336
 _tp_marshal_VOID__BOXED_BOXED_BOXED_BOXED_UINT64_BOXED_POINTER (closure=0x7fff1a676bd0, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x25b4400, invocation_hint=<optimized out>, marshal_data=<optimized out>) at _gen/signals-marshal.c:452
 invoke_object_method (message=0x25a5f10, connection=0x24ebc40, method=0x7ffd0eee9ca0, object_info=0x7ffd0eee7e00, object=0x25d11b0) at dbus-gobject.c:1744
 object_registration_message (connection=0x24ebc40, message=0x25a5f10, user_data=<optimized out>) at dbus-gobject.c:1968
 ?? () from /tmp/tmp2wysig/lib/x86_64-linux-gnu/libdbus-1.so.3

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
description: updated
Changed in empathy:
importance: Unknown → Critical
status: Unknown → New
Changed in empathy (Ubuntu):
status: New → Triaged
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

I'm creating report in bugs.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=40356

affects: empathy → telepathy-glib
Changed in telepathy-glib:
importance: Critical → Unknown
status: New → Unknown
affects: empathy (Ubuntu) → telepathy-glib (Ubuntu)
Changed in telepathy-glib:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Will Thompson (wjt) wrote :

Looking at base-client.c:2336:

2332 channel = ensure_channel (self, connection, chan_path, chan_props,
2333 &error);
2334 if (channel == NULL)
2335 {
2336 → DEBUG ("Failed to create TpChannel: %s", error->message);
2337 goto out;
2338 }

This plus:

SegvReason: reading NULL VMA

suggests to me that 'error' is NULL, which suggests to me that 'ensure_channel' (or rather, something within it) is hitting g_return_if_fail().

From the .xsession-errors file, a few instances of:

(empathy:26326): empathy-CRITICAL **: empathy_contact_get_account: assertion `EMPATHY_IS_CONTACT (contact)' failed

are the only criticals I see. From ProcStatus.txt:

Pid: 28326

Soooooooo this looks like Empathy is probably at fault here.

Revision history for this message
In , Andre Klapper (a9016009) wrote :

> Soooooooo this looks like Empathy is probably at fault here.

If this is still an issue nowadays, please report to Empathy.

Changed in telepathy-glib:
status: Confirmed → Won't Fix
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.