Description of problem: I doubleclicked a contact to open chat window and it opened and crashed immediately. It happens with this (and so far only this) contact consistently even after deleting all logs (~/.local/share/Tplogger or something like that) and rebooting after deleting logs. Also after removing and adding this contact. Version-Release number of selected component: empathy-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: tpl_log_iter_pidgin_get_events executable: /usr/libexec/empathy-chat kernel: 3.9.4-300.fc19.x86_64 runlevel: N 5 uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (6 frames) #0 tpl_log_iter_pidgin_get_events at log-iter-pidgin.c:87 #1 tpl_log_walker_fill_cache_async_thread at log-walker.c:310 #2 run_in_thread at gsimpleasyncresult.c:871 #3 io_job_thread at gioscheduler.c:89 #4 g_task_thread_pool_thread at gtask.c:1242 #6 g_thread_proxy at gthread.c:798
Created attachment 757322 [details] File: backtrace
Created attachment 757323 [details] File: cgroup
Created attachment 757324 [details] File: core_backtrace
Created attachment 757325 [details] File: dso_list
Created attachment 757326 [details] File: environ
Created attachment 757327 [details] File: limits
Created attachment 757328 [details] File: maps
Created attachment 757329 [details] File: open_fds
Created attachment 757330 [details] File: proc_pid_status
Created attachment 757331 [details] File: var_log_messages
I found out that this was the only contact that had some logs in ~/.purple/logs. After deleting those, there is no more error.
Created attachment 783304 [details] Skip invalid entries while iterate This patch allows at least open a new chat-window and existing one's won't be closed. But the history is not shown.
Created attachment 784240 [details] Skip invalid entries while iterate v2 I spend a couple more minutes for this, so patch works much better, because we get the history. But still this is only a workaround to avoid the crash. Since the chat is working properly as part of a gnome-shell notification, the real problem is not the iteration it self.
This bug tracked upstream under: https://bugs.freedesktop.org/show_bug.cgi?id=63458
Also applies to Fedora 20. Can we update the version? https://retrace.fedoraproject.org/faf/reports/204155/
Also applies to Fedora 21 alpha.
Created attachment 943177 [details] Update rpm to v0.8.1 and add the patch
Created attachment 943178 [details] Update rpm to v0.8.1 and add the patch v2
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.