telepathy-idle crashes very often when I leave IRC rooms idle for a little while. Hope the trace is good enough - please ask if you need me to play with gdb and valgrind. I'm using version 5.5.4 telepathy-idle 0.1.6 on Ubuntu 10.10. (Ubuntu report on https://bugs.launchpad.net/ubuntu/+source/telepathy-idle/+bug/643689) #0 0x00c7a416 in __kernel_vsyscall () No symbol table info available. #1 0x00665941 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <value optimized out> pid = 7950324 selftid = 1912 #2 0x00668e42 in *__GI_abort () at abort.c:92 act = {__sigaction_handler = {sa_handler = 0xbff04e34, sa_sigaction = 0xbff04e34}, sa_mask = {__val = {5864386, 3220196900, 9091896, 3220196888, 5945972, 0, 3077482064, 1, 0, 1, 3077495488, 7659893, 1880052, 1818453, 145158640, 0, 3220196824, 1731941, 0, 3220196960, 3220196888, 3220196900, 2, 3077495488, 0, 7951744, 4294967295, 9132646, 7951744, 7951815, 3220196892, 6958431}}, sa_flags = 7951744, sa_restorer = 0x7955c7 <_IO_2_1_stderr_+71>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0x00905f56 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #4 0x00906377 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #5 0x009075c2 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #6 0x00907f24 in g_slice_free1 () from /lib/libglib-2.0.so.0 No symbol table info available. #7 0x00ea7108 in _pending_free (msg=0x8ab65b0, contacts_repo=0x8a68e60) at text-mixin.c:243 No locals. #8 0x00ea77d6 in tp_text_mixin_acknowledge_pending_messages (obj=0x8a87860, ids=0x8a91da8, error=0xbff0508c) at text-mixin.c:432 mixin = (TpTextMixin *) 0x8a87888 msg = <value optimized out> i = 14 __PRETTY_FUNCTION__ = "tp_text_mixin_acknowledge_pending_messages" #9 0x00ea7846 in tp_text_mixin_acknowledge_pending_messages_async ( iface=0x8a87860, ids=0x8a91da8, context=0x8a97c98) at text-mixin.c:446 error = (GError *) 0x0 #10 0x00eb1c7a in tp_svc_channel_type_text_acknowledge_pending_messages ( self=0x8a87860, in_IDs=0x8a91da8, context=0x8a97c98) at _gen/tp-svc-channel.c:3889 impl = (tp_svc_channel_type_text_acknowledge_pending_messages_impl) 0 #11 0x00eac78f in _tp_marshal_VOID__BOXED_POINTER (closure=0xbff05204, return_value=0x0, n_param_values=3, param_values=0x8a91768, invocation_hint=0x0, marshal_data=0xeb1c30) at _gen/signals-marshal.c:496 data1 = (gpointer) 0x6 data2 = <value optimized out> __PRETTY_FUNCTION__ = "_tp_marshal_VOID__BOXED_POINTER" #12 0x009ebddf in invoke_object_method (object=<value optimized out>, object_info=<value optimized out>, method=0xee9560, connection=0x8a6ffc0, message=0x8aa3400) at dbus-gobject.c:1724 had_error = <value optimized out> send_reply = 1 gerror = (GError *) 0x0 value_array = (GValueArray *) 0x8a94e90 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}}} 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} in_signature = 0x8a831b0 "au" out_param_values = (GArray *) 0x471d45 out_param_gvalues = (GValueArray *) 0xbff051a8 out_param_count = 145258592 out_param_pos = 145258592 out_param_gvalue_pos = 4 result = DBUS_HANDLER_RESULT_HANDLED reply = <value optimized out> have_retval = 6472769 retval_signals_error = -1074769528 retval_is_synthetic = 4 retval_is_constant = 8 arg_metadata = <value optimized out> #13 0x009ec38e in object_registration_message (connection=0x8a6ffc0, message=0x8aa3400, user_data=0x8a829b0) at dbus-gobject.c:1944 pspec = (GParamSpec *) 0xee9560 setter = 0 getter = 145460424 getall = <value optimized out> s = 0x8a831b0 "au" requested_propname = <value optimized out> wincaps_propiface = <value optimized out> iter = {dummy1 = 0x8a73cf8, dummy2 = 0x1caff4, dummy3 = 1880792, dummy4 = 1880052, dummy5 = -1074768904, dummy6 = 1812242, dummy7 = 0, dummy8 = 0, dummy9 = -1074768856, dummy10 = 1766374, dummy11 = 0, pad1 = 0, pad2 = -1074768712, pad3 = 0x8a6f16c} method = (const DBusGMethodInfo *) 0xee9560 object_info = (const DBusGObjectInfo *) 0xee8724 ret = <value optimized out> #14 0x001af6ee in _dbus_object_tree_dispatch_and_unlock (tree=0x8a6cf90, message=0x8aa3400) at dbus-object-tree.c:856 user_data = <value optimized out> next = (DBusList *) 0x0 path = (char **) 0x8a903e0 exact_match = 0 list = (DBusList *) 0x8a6f16c link = <value optimized out> result = <value optimized out> subtree = <value optimized out> #15 0x001a23b7 in dbus_connection_dispatch (connection=0x8a6ffc0) at dbus-connection.c:4492 message = <value optimized out> link = <value optimized out> filter_list_copy = (DBusList *) 0x0 message_link = (DBusList *) 0x8a6f1f0 result = <value optimized out> status = <value optimized out> __FUNCTION__ = "dbus_connection_dispatch" #16 0x009e839d in message_queue_dispatch (source=0x8a719e8, callback=0, user_data=0x0) at dbus-gmain.c:101 connection = (DBusConnection *) 0x8a6ffc0 #17 0x008e8015 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 No symbol table info available. #18 0x008ebe28 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #19 0x008ec367 in g_main_loop_run () from /lib/libglib-2.0.so.0 No symbol table info available. #20 0x00ea59af in tp_run_connection_manager ( prog_name=0x8061edb "telepathy-idle", version=0x8061ed5 "0.1.6", construct_cm=0x804d940 <_construct_cm>, argc=1, argv=0xbff05814) at run.c:285 connection = (DBusConnection *) 0x8a6ffc0 bus_daemon = <value optimized out> error = (GError *) 0x0 ret = 134643844 __PRETTY_FUNCTION__ = "tp_run_connection_manager" #21 0x0804d92a in main (argc=1, argv=0xbff05814) at idle.c:47 debug_sender = (TpDebugSender *) 0x8a68030 result = <value optimized out>
*** This bug has been marked as a duplicate of bug 29103 ***
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.