Description of problem: I was only adding twitter account and crashed on verifying Version-Release number of selected component: telepathy-gabble-0.17.4-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: stun_server_resolved_cb executable: /usr/libexec/telepathy-gabble kernel: 3.9.6-301.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 stun_server_resolved_cb at wocky-jingle-info.c:277 #1 g_task_return_now at gtask.c:1105 #2 g_task_return at gtask.c:1158 #3 _g_closure_invoke_va at gclosure.c:840 #6 g_cancellable_cancel at gcancellable.c:507 #7 weak_refs_notify at gobject.c:2470 #9 wocky_jingle_factory_dispose at wocky-jingle-factory.c:149 #11 gabble_jingle_mint_dispose at jingle-mint.c:151 #13 gabble_connection_dispose at connection.c:1289 #17 tp_base_connection_finish_shutdown at base-connection.c:2864
Created attachment 764608 [details] File: backtrace
Created attachment 764609 [details] File: cgroup
Created attachment 764610 [details] File: core_backtrace
Created attachment 764611 [details] File: dso_list
Created attachment 764612 [details] File: environ
Created attachment 764613 [details] File: limits
Created attachment 764614 [details] File: maps
Created attachment 764615 [details] File: open_fds
Created attachment 764616 [details] File: proc_pid_status
Created attachment 764617 [details] File: var_log_messages
I tried to connect to the Facebook and Google XMPP services. I got an SSL certificate error, then set my status to "Offline," to stop connecting. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: stun_server_resolved_cb executable: /usr/libexec/telepathy-gabble kernel: 3.10.5-201.fc19.x86_64 package: telepathy-gabble-0.17.5-2.fc19 reason: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
After waking up from hibernation I got the ABRT message that telepathy-gabbloe had crashed. This is the first occurence, so I do not have much more information as to how to reproduce it. Uptime was 3 1/2 days, with several hibernation/thaw events happening. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: stun_server_resolved_cb executable: /usr/libexec/telepathy-gabble kernel: 3.11.7-200.fc19.i686.PAE package: telepathy-gabble-0.18.1-1.fc19 reason: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1001
Seemingly-random crash. My presence was set to active (by GNOME Shell) in both my Facebook and Google account, I wasn't actively using either. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: stun_server_resolved_cb executable: /usr/libexec/telepathy-gabble kernel: 3.11.10-200.fc19.x86_64 package: telepathy-gabble-0.18.1-1.fc19 reason: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.