Hide Forgot
Version-Release number of selected component: empathy-3.10.3-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: g_variant_type_info_check executable: /usr/libexec/empathy-chat kernel: 3.15.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 g_variant_type_info_check at gvarianttypeinfo.c:164 #1 g_variant_type_info_get_type_string at gvarianttypeinfo.c:200 #2 g_variant_get_type at gvariant.c:2073 #3 append_value_to_blob at gdbusmessage.c:2426 #4 append_body_to_blob at gdbusmessage.c:2542 #5 g_dbus_message_to_blob at gdbusmessage.c:2711 Potential duplicate: bug 1079665
Created attachment 927557 [details] File: backtrace
Created attachment 927558 [details] File: cgroup
Created attachment 927559 [details] File: core_backtrace
Created attachment 927560 [details] File: dso_list
Created attachment 927561 [details] File: environ
Created attachment 927562 [details] File: exploitable
Created attachment 927563 [details] File: limits
Created attachment 927564 [details] File: maps
Created attachment 927565 [details] File: open_fds
Created attachment 927566 [details] File: proc_pid_status
Created attachment 927567 [details] File: var_log_messages
Another user experienced a similar problem: Empathy worked for me last week. On Friday, I ran yum upgrade before leaving work, then ran it again on arriving this morning (Monday). That gave me a new kernel, 3.15.10-200.fc20.x86_64, so I rebooted. Now I can't get empathy to work. When I start it, I see the contact list for a split second, then it disappears. Then the window for the room I hang out in all day opens. If I type in the room window, everything is fine. But the second that mouse focus leaves that window, it disappears, too. ABRT shows three separate crashes for empathy, which is suspicious. Something lower down in the stack must have changed. I will file bugs for all 3 crashes in case that yields a clue as to what is really going on. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: g_variant_type_info_check executable: /usr/libexec/empathy-chat kernel: 3.15.10-200.fc20.x86_64 package: empathy-3.10.3-2.fc20 reason: empathy-chat killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Crashes when starting empathy after applying updates up to Aug 18. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: g_variant_type_info_check executable: /usr/libexec/empathy-chat kernel: 3.15.10-200.fc20.x86_64 package: empathy-3.10.3-2.fc20 reason: empathy-chat killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Start Empathy from Gnome-Dash. The roster opens and then closes after some seconds reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: empathy crash_function: g_variant_type_info_check executable: /usr/bin/empathy kernel: 3.15.10-200.fc20.x86_64 package: empathy-3.10.3-2.fc20 reason: empathy killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
For the benefit of those stumbling across this problem, it turns out that the triggering event is updating to zeitgeist-0.9.14-3. Downgrading to zeitgeist-0.9.14-2 fixes the problem for me.
(In reply to Jerry James from comment #15) > For the benefit of those stumbling across this problem, it turns out that > the triggering event is updating to zeitgeist-0.9.14-3. Downgrading to > zeitgeist-0.9.14-2 fixes the problem for me. Yes, downgrading to 0.9.14-2 fixed it. See Bug 1130769.
The latest zeitgeist packages as mentioned in Bug 1130769 seems to fix the problem for me: zeitgeist.x86_64 0.9.16-0.2.20140808.git.ce9affa.fc20 zeitgeist-libs.x86_64 0.9.16-0.2.20140808.git.ce9affa.fc20
*** Bug 1131606 has been marked as a duplicate of this bug. ***
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.