Bug 25944 - Salut crashes when connecting
Summary: Salut crashes when connecting
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: salut (show other bugs)
Version: 0.8
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-07 17:52 UTC by Olivier Crête
Modified: 2010-01-08 03:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Olivier Crête 2010-01-07 17:52:53 UTC
Here is the result from the crash

(gdb) bt full
#0  salut_self_set_presence (self=0x0, status=SALUT_PRESENCE_AVAILABLE, message=0x0, error=0xbecc7f9c) at salut-self.c:527
        __PRETTY_FUNCTION__ = "salut_self_set_presence"
#1  0x00016b40 in set_own_status (obj=<value optimized out>, status=0xbecc7fd4, error=0xbecc7fe4) at salut-connection.c:605
        self = 0x99030
        ret = <value optimized out>
        err = 0x0
        value = <value optimized out>
        message = 0x0
        presence = SALUT_PRESENCE_AVAILABLE
#2  0x4048470c in tp_presence_mixin_simple_presence_set_presence (iface=0x99030, status=0x94998 "available", message=0x9ed88 "", context=0x8f810)
    at presence-mixin.c:1192
        obj = 0x0
        status_to_set = {index = 0, optional_arguments = 0x0, _future1 = 0x0, _future2 = 0x0}
        s = <value optimized out>
        error = 0x0
        optional_arguments = 0x0
        __PRETTY_FUNCTION__ = "tp_presence_mixin_simple_presence_set_presence"
#3  0x4049ce70 in tp_svc_connection_interface_simple_presence_set_presence (self=0x99030, in_Status=0x94998 "available", in_Status_Message=0x9ed88 "", 
    context=0x8f810) at _gen/tp-svc-connection.c:3165
        impl = 0x2
#4  0x40491a0c in _tp_marshal_VOID__STRING_STRING_POINTER (closure=0xbecc826c, return_value=<value optimized out>, n_param_values=<value optimized out>, 
    param_values=0x947c8, invocation_hint=0x0, marshal_data=0x4049ce24) at _gen/signals-marshal.c:1410
        data1 = 0x99030
        data2 = <value optimized out>
        __PRETTY_FUNCTION__ = "_tp_marshal_VOID__STRING_STRING_POINTER"
#5  0x4025efac in ?? () from /usr/lib/libdbus-glib-1.so.2
No symbol table info available.
#6  0x4025efac in ?? () from /usr/lib/libdbus-glib-1.so.2
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) f 1
#1  0x00016b40 in set_own_status (obj=<value optimized out>, status=0xbecc7fd4, error=0xbecc7fe4) at salut-connection.c:605
605	salut-connection.c: No such file or directory.
	in salut-connection.c
(gdb) p *(SalutConnectionPrivate*) self->priv
$1 = {dispose_has_run = 0, published_name = 0x98e38 "root", nickname = 0x9e3c0 "C", first_name = 0x967a0 "S", last_name = 0x96980 "S", jid = 0x0, 
  email = 0x0, olpc_color = 0x0, olpc_key = 0x0, discovery_client = 0x934c0, self = 0x0, xmpp_connection_manager = 0x9c810, contact_manager = 0x92138, 
  im_manager = 0x8af20, muc_manager = 0x92238, ft_manager = 0x91a50, roomlist_manager = 0x92270, tubes_manager = 0x0, si_bytestream_manager = 0x0, 
  olpc_activity_manager = 0x91990, backend_type = 601288}


And some relavant package versions
ii  telepathy-salut                                     0.3.9-1                          Link-local XMPP connection manager for the Telepathy 
ii  libtelepathy-glib0                                  0.8.1-0maemo1+0m5                Telepathy framework - GLib library
ii  libdbus-glib-1-2                                    0.78-0maemo6+0m5                 simple interprocess messaging system (GLib-based shar
Comment 1 Jonny Lamb 2010-01-08 03:35:31 UTC
(In reply to comment #0)
> #0  salut_self_set_presence (self=0x0, status=SALUT_PRESENCE_AVAILABLE,
> message=0x0, error=0xbecc7f9c) at salut-self.c:527

This is because MC5 is setting a presence before you're online. This is fixed in 0.3.10.

I haven't packaged 0.3.10 for fremantle yet because it depends on a too new telepathy-glib.

Anyway, already fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.