Bug 891581

Summary: [abrt] empathy-3.6.2-2.fc18: g_type_check_instance_cast: Process /usr/libexec/empathy-chat was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dušan <prescott66>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d624788c3d1e9256fe4a8b6de4f5b6452f0a601d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:22:06 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 Dušan 2013-01-03 10:53:06 UTC 
Description of problem:
1.search contact(from google account) in gnome shell activity view
2.click on contact
3.click on icon to send instant message
4.get this crash

Version-Release number of selected component:
empathy-3.6.2-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/empathy-chat
crash_function: g_type_check_instance_cast
executable:     /usr/libexec/empathy-chat
kernel:         3.6.11-3.fc18.x86_64
remote_result:  765994
uid:            1000
var_log_messages: Jan  3 11:45:15 localhost abrt[4853]: Saved core dump of pid 4847 (/usr/libexec/empathy-chat) to /var/spool/abrt/ccpp-2013-01-03-11:45:14-4847 (54386688 bytes)

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 g_type_check_instance_cast at gtype.c:3997
 #1 _tpl_event_queue_insert_sorted_after at util.c:128
 #2 _tpl_log_manager_get_filtered_events at log-manager.c:595
 #3 _get_filtered_events_async_thread at log-manager.c:1091
 #4 run_in_thread at gsimpleasyncresult.c:869
 #5 io_job_thread at gioscheduler.c:162
 #7 g_thread_proxy at gthread.c:797
Comment 1 Dušan 2013-01-03 10:53:11 UTC 
Created attachment 671968 [details]
File: backtrace
Comment 2 Dušan 2013-01-03 10:53:14 UTC 
Created attachment 671969 [details]
File: cgroup
Comment 3 Dušan 2013-01-03 10:53:16 UTC 
Created attachment 671970 [details]
File: core_backtrace
Comment 4 Dušan 2013-01-03 10:53:19 UTC 
Created attachment 671971 [details]
File: dso_list
Comment 5 Dušan 2013-01-03 10:53:21 UTC 
Created attachment 671972 [details]
File: environ
Comment 6 Dušan 2013-01-03 10:53:23 UTC 
Created attachment 671973 [details]
File: limits
Comment 7 Dušan 2013-01-03 10:53:26 UTC 
Created attachment 671974 [details]
File: maps
Comment 8 Dušan 2013-01-03 10:53:28 UTC 
Created attachment 671975 [details]
File: open_fds
Comment 9 Dušan 2013-01-03 10:53:31 UTC 
Created attachment 671976 [details]
File: proc_pid_status
Comment 10 Fedora End Of Life 2013-12-21 10:10:02 UTC 
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.
Comment 11 Fedora End Of Life 2014-02-05 14:22:09 UTC 
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.