Bug 1006903

Summary: [abrt] telepathy-haze-0.7.0-4.fc19: g_type_check_instance_cast: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mib
Component: telepathy-hazeAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:085d7e55d584d72deec1a30c7b0fb7f680293327
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:08:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mib 2013-09-11 13:29:41 UTC
Version-Release number of selected component:
telepathy-haze-0.7.0-4.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-haze
crash_function: g_type_check_instance_cast
executable:     /usr/libexec/telepathy-haze
kernel:         3.10.5-201.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at /lib64/libgobject-2.0.so.0
 #1 disconnected_cb
 #2 _purple_connection_destroy at connection.c:287
 #3 purple_account_disconnect at account.c:1284
 #4 purple_connection_disconnect_cb at connection.c:523
 #5 g_timeout_dispatch at /lib64/libglib-2.0.so.0
 #6 g_main_context_dispatch at /lib64/libglib-2.0.so.0
 #7 g_main_context_iterate.isra.22 at /lib64/libglib-2.0.so.0
 #8 g_main_loop_run at /lib64/libglib-2.0.so.0
 #9 tp_run_connection_manager at run.c:285

Potential duplicate: bug 885695

Comment 1 mib 2013-09-11 13:29:45 UTC
Created attachment 796365 [details]
File: backtrace

Comment 2 mib 2013-09-11 13:29:48 UTC
Created attachment 796366 [details]
File: cgroup

Comment 3 mib 2013-09-11 13:29:51 UTC
Created attachment 796367 [details]
File: core_backtrace

Comment 4 mib 2013-09-11 13:29:54 UTC
Created attachment 796368 [details]
File: dso_list

Comment 5 mib 2013-09-11 13:29:57 UTC
Created attachment 796369 [details]
File: environ

Comment 6 mib 2013-09-11 13:30:00 UTC
Created attachment 796370 [details]
File: exploitable

Comment 7 mib 2013-09-11 13:30:03 UTC
Created attachment 796371 [details]
File: limits

Comment 8 mib 2013-09-11 13:30:07 UTC
Created attachment 796373 [details]
File: maps

Comment 9 mib 2013-09-11 13:30:11 UTC
Created attachment 796374 [details]
File: open_fds

Comment 10 mib 2013-09-11 13:30:14 UTC
Created attachment 796375 [details]
File: proc_pid_status

Comment 11 mib 2013-09-11 13:30:18 UTC
Created attachment 796376 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-01-09 19:48:10 UTC
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.

Comment 13 Fedora End Of Life 2015-02-17 17:08:58 UTC
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.