Hide Forgot
Description of problem: This happened near to bug #1042994 so may be related. Version-Release number of selected component: empathy-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: strlen executable: /usr/libexec/empathy-chat kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 g_strdup at gstrfuncs.c:363 #2 org_bluez_obex_phonebook_access_phonebook_entry_copy at org-bluez-obex-client.c:602 #3 _folks_backends_blue_z_persona_store_update_contacts_from_file_co at bluez-persona-store.c:1058 #4 g_task_return_now at gtask.c:1108 #5 complete_in_idle_cb at gtask.c:1117 #9 g_main_context_iteration at gmain.c:3774 #10 g_application_run at gapplication.c:1635
Created attachment 836426 [details] File: backtrace
Created attachment 836427 [details] File: cgroup
Created attachment 836428 [details] File: core_backtrace
Created attachment 836429 [details] File: dso_list
Created attachment 836430 [details] File: environ
Created attachment 836431 [details] File: exploitable
Created attachment 836432 [details] File: limits
Created attachment 836433 [details] File: maps
Created attachment 836434 [details] File: open_fds
Created attachment 836435 [details] File: proc_pid_status
Created attachment 836436 [details] File: var_log_messages
I encountered this crash while launching Empathy. Running in a terminal revealed: (empathy:2792): bluez-CRITICAL **: folks_backends_blue_z_persona_construct: assertion 'vcf != NULL' failed Segmentation fault (core dumped) I had recently added a tethered Bluetooth network connection, so I went into the Bluetooth control panel and deleted the pairing with my mobile phone. After that, Empathy launched correctly.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.