Description of problem: How did this problem happen: Starting first time telepathy How can it be reproduced null Version-Release number of selected component: telepathy-salut-0.8.0-2.fc18 Additional info: libreport version: 2.0.17 abrt_version: 2.0.17 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-salut crash_function: tp_base_channel_close_dbus kernel: 3.6.3-3.fc18.x86_64 truncated backtrace: :Thread no. 1 (6 frames) : #2 tp_base_channel_close_dbus at base-channel.c:1126 : #3 ffi_call_unix64 at ../src/x86/unix64.S:75 : #4 ffi_call at ../src/x86/ffi64.c:486 : #5 g_cclosure_marshal_generic at gclosure.c:1454 : #7 object_registration_message at dbus-gobject.c:2161 : #15 tp_run_connection_manager at run.c:285
Created attachment 634280 [details] File: core_backtrace
Created attachment 634281 [details] File: environ
Created attachment 634282 [details] File: backtrace
Created attachment 634283 [details] File: limits
Created attachment 634284 [details] File: cgroup
Created attachment 634285 [details] File: executable
Created attachment 634286 [details] File: maps
Created attachment 634287 [details] File: dso_list
Created attachment 634288 [details] File: proc_pid_status
Created attachment 634289 [details] File: var_log_messages
Created attachment 634290 [details] File: open_fds
I meant starting first time EMPATHY.
Actually I can add more information: 1) When connecting to a new room via [ROOM] [JOIN] 2) then adding a new room name into section ROOM: # make message when people nearby is actived "people nearby internal error"
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.