Description of problem: Left call (dialing) dialog open and came back after some time. Thw message dialog saying "you do not have a valid account to make a call" was up and rakia had crashed. Version-Release number of selected component: telepathy-rakia-0.7.4-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/telepathy-rakia crash_function: g_return_if_fail_warning executable: /usr/libexec/telepathy-rakia kernel: 3.8.4-202.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #2 g_return_if_fail_warning at gmessages.c:1012 #3 g_source_remove_poll at gmain.c:1277 #4 su_source_unregister_all at su_source.c:857 #5 su_port_unregister_all at su_port.h:300 #6 su_root_destroy at su_root.c:522 #7 rakia_connection_manager_finalize at sip-connection-manager.c:128 #9 quit_loop at run.c:72 #10 kill_connection_manager at run.c:83 #16 tp_run_connection_manager at run.c:285 Potential duplicate: bug 842861
Created attachment 730952 [details] File: backtrace
Created attachment 730953 [details] File: cgroup
Created attachment 730954 [details] File: core_backtrace
Created attachment 730955 [details] File: dso_list
Created attachment 730956 [details] File: environ
Created attachment 730957 [details] File: limits
Created attachment 730958 [details] File: maps
Created attachment 730959 [details] File: open_fds
Created attachment 730960 [details] File: proc_pid_status
Created attachment 730961 [details] File: smolt_data
Created attachment 730962 [details] File: var_log_messages
Left sip account connected overnight but connection was lost (VPN). Logged on in morning to see bug report. backtrace_rating: 4 cmdline: /usr/libexec/telepathy-rakia crash_function: g_return_if_fail_warning executable: /usr/libexec/telepathy-rakia kernel: 3.8.4-202.fc18.x86_64 package: telepathy-rakia-0.7.4-2.fc18 reason: Process /usr/libexec/telepathy-rakia was killed by signal 5 (SIGTRAP) uid: 1000 ureports_counter: 1
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.