Version-Release number of selected component: empathy-3.6.0-2.fc18 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: empathy crash_function: event_remove kernel: 3.6.0-3.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 event_remove at empathy-event-manager.c:179 : #1 ffi_call_unix64 at ../src/x86/unix64.S:75 : #2 ffi_call at ../src/x86/ffi64.c:486 : #3 g_cclosure_marshal_generic_va at gclosure.c:1550 : #4 _g_closure_invoke_va at gclosure.c:840 : #12 g_signal_emitv at gsignal.c:3041 : #13 gtk_binding_entry_activate at gtkbindings.c:651 : #14 binding_activate at gtkbindings.c:1523 : #15 gtk_bindings_activate_list at gtkbindings.c:1584 : #16 gtk_bindings_activate_event at gtkbindings.c:1669
Created attachment 623288 [details] File: core_backtrace
Created attachment 623289 [details] File: environ
Created attachment 623290 [details] File: backtrace
Created attachment 623291 [details] File: limits
Created attachment 623292 [details] File: cgroup
Created attachment 623293 [details] File: maps
Created attachment 623294 [details] File: dso_list
Created attachment 623295 [details] File: var_log_messages
Created attachment 623296 [details] File: open_fds
There was blinking icon near one contact as a new messege would come (but I had already read that message). So I double clicked on that contact, icon change to the 'online'. Then I clicked on another contact and the window with contact crashed (disappeared). backtrace_rating: 4 Package: empathy-3.6.1-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Could you verify that this bug is still present in the latest release? Haven't been able to reproduce this on my machine. Thanks.
I have seen it occurring a few times, always when shutting down my computer with empathy still connected. However, usually everything goes smooth and I cannot recognize what exactly causes the problem... Using: empathy-3.6.3-1.fc18 (x86_64)
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days