Bug 991642

Summary: [abrt] empathy-3.8.3-1.fc19: tpl_log_iter_xml_get_events: Process /usr/libexec/empathy-chat was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: lemovice <lemovice>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bdpepple, jon.dufresne, louis, nirmal.pathak, soeren.grunewald, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d9f0c82411ea36cbb644d6f163f7b04de4241fce
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:09:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description lemovice 2013-08-03 08:35:58 UTC 
Description of problem:
au demarrage de telepathy, avec une integration de skype

Version-Release number of selected component:
empathy-3.8.3-1.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/libexec/empathy-chat
crash_function: tpl_log_iter_xml_get_events
executable:     /usr/libexec/empathy-chat
kernel:         3.10.4-300.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Aug  3 10:18:37 PO25628 abrt[2232]: Saved core dump of pid 2225 (/usr/libexec/empathy-chat) to /var/tmp/abrt/ccpp-2013-08-03-10:18:36-2225 (53641216 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 tpl_log_iter_xml_get_events at log-iter-xml.c:88
 #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
Comment 1 lemovice 2013-08-03 08:36:03 UTC 
Created attachment 782246 [details]
File: backtrace
Comment 2 lemovice 2013-08-03 08:36:06 UTC 
Created attachment 782247 [details]
File: cgroup
Comment 3 lemovice 2013-08-03 08:36:10 UTC 
Created attachment 782248 [details]
File: core_backtrace
Comment 4 lemovice 2013-08-03 08:36:15 UTC 
Created attachment 782249 [details]
File: dso_list
Comment 5 lemovice 2013-08-03 08:36:19 UTC 
Created attachment 782250 [details]
File: environ
Comment 6 lemovice 2013-08-03 08:36:23 UTC 
Created attachment 782251 [details]
File: limits
Comment 7 lemovice 2013-08-03 08:36:27 UTC 
Created attachment 782252 [details]
File: maps
Comment 8 lemovice 2013-08-03 08:36:30 UTC 
Created attachment 782253 [details]
File: open_fds
Comment 9 lemovice 2013-08-03 08:36:33 UTC 
Created attachment 782254 [details]
File: proc_pid_status
Comment 10 Soeren Grunewald 2013-08-06 12:10:38 UTC 
This issue is quite similar to #971112
Comment 11 Soeren Grunewald 2013-08-12 18:38:34 UTC 
The patch https://bugzilla.redhat.com/attachment.cgi?id=784240&action=diff solves this issue too.
Comment 12 Soeren Grunewald 2013-10-15 19:41:52 UTC 
This bug tracked upstream under:
https://bugs.freedesktop.org/show_bug.cgi?id=63458
Comment 13 Jon Dufresne 2014-04-15 18:45:54 UTC 
Occurs for me in F20.

Happens when I open a chat window for a specific person and only that person. I'm guessing something in the chat logs is creating an issue? I deleted the logs and the problem went away.
Comment 14 Fedora End Of Life 2015-05-29 09:14:20 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.
Comment 15 Fedora End Of Life 2015-06-29 12:09:08 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.