Version-Release number of selected component: empathy-3.11.92-1.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: empathy crash_function: g_variant_type_info_check executable: /usr/bin/empathy kernel: 3.14.0-0.rc7.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_variant_type_info_check at gvarianttypeinfo.c:162 #1 g_variant_type_info_get_type_string at gvarianttypeinfo.c:198 #2 g_variant_get_type at gvariant.c:2031 #3 append_value_to_blob at gdbusmessage.c:2424 #4 append_body_to_blob at gdbusmessage.c:2540 #5 g_dbus_message_to_blob at gdbusmessage.c:2709 #6 g_dbus_connection_send_message_unlocked at gdbusconnection.c:1659 #7 g_dbus_connection_send_message_with_reply_unlocked at gdbusconnection.c:1993 #8 g_dbus_connection_send_message_with_reply at gdbusconnection.c:2097 #9 zeitgeist_remote_log_proxy_find_events_async at remote.c:739
Created attachment 877639 [details] File: backtrace
Created attachment 877640 [details] File: cgroup
Created attachment 877641 [details] File: core_backtrace
Created attachment 877642 [details] File: dso_list
Created attachment 877644 [details] File: environ
Created attachment 877646 [details] File: exploitable
Created attachment 877648 [details] File: limits
Created attachment 877650 [details] File: maps
Created attachment 877652 [details] File: open_fds
Created attachment 877654 [details] File: proc_pid_status
Created attachment 877656 [details] File: var_log_messages
Another user experienced a similar problem: Crash after adding a Jabber account (dukgo.com) reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: g_variant_type_info_check executable: /usr/libexec/empathy-chat kernel: 3.14.0-0.rc8.git0.1.fc21.i686 package: empathy-3.12.0-1.fc21 reason: empathy-chat killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Downgrade zeitgeist-libs resolves issues zeitgeist-libs-0.9.14-3.fc20.x86_64 -> zeitgeist-libs-0.9.14-2.fc20.x86_64 Prior to downgrade error for me was: (empathy:20503): folks-WARNING **: backend-store.vala:409: Error preparing Backend 'bluez': No BlueZ 5 object manager running, so the BlueZ backend will be inactive. Either your BlueZ installation is too old (only version 5 is supported) or the service can’t be started. (empathy:20503): folks-WARNING **: backend-store.vala:409: Error preparing Backend 'ofono': No oFono object manager running, so the oFono backend will be inactive. Either oFono isn’t installed or the service can’t be started. (empathy:20503): GLib-CRITICAL **: g_variant_ref: assertion 'value->ref_count > 0' failed (empathy:20503): GLib-CRITICAL **: g_variant_unref: assertion 'value->ref_count > 0' failed (empathy:20503): GLib-CRITICAL **: g_variant_ref: assertion 'value->ref_count > 0' failed (empathy:20503): GLib-CRITICAL **: g_variant_unref: assertion 'value->ref_count > 0' failed (empathy:20503): telepathy-CRITICAL **: _logger_logger_vanished: assertion 'conn != NULL' failed (empathy:20503): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (empathy:20503): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (empathy:20503): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (empathy:20503): telepathy-CRITICAL **: _logger_logger_vanished: assertion 'conn != NULL' failed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
no comments for long time.