Bug 1032242

Summary: [abrt] telepathy-haze-0.8.0-1.fc20: g_return_if_fail_warning: Process /usr/libexec/telepathy-haze was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Martin Meyer <elreydetodo>
Component: telepathy-hazeAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/00ce9b4d9a92b36b06a27e11643004088cd758cd
Whiteboard: abrt_hash:f3812f4bec4cb05166801ba0d60f2ea182656430
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:02:37 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 Martin Meyer 2013-11-19 19:01:26 UTC
Description of problem:
Crashing seems random, time until crash seems random. It always seems to happen within an hour of GOA being reloaded.

Version-Release number of selected component:
telepathy-haze-0.8.0-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-haze
crash_function: g_return_if_fail_warning
executable:     /usr/libexec/telepathy-haze
kernel:         3.11.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_return_if_fail_warning at gmessages.c:1034
 #3 tp_asv_get_string at dbus.c:984
 #4 haze_connection_update_capabilities at connection-capabilities.c:256
 #5 ffi_call_unix64 at ../src/x86/unix64.S:76
 #6 ffi_call at ../src/x86/ffi64.c:522
 #7 g_cclosure_marshal_generic at gclosure.c:1454
 #8 invoke_object_method at dbus-gobject.c:1899
 #9 object_registration_message at dbus-gobject.c:2161
 #10 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #17 tp_run_connection_manager at run.c:285

Potential duplicate: bug 987911

Comment 1 Martin Meyer 2013-11-19 19:01:35 UTC
Created attachment 826243 [details]
File: backtrace

Comment 2 Martin Meyer 2013-11-19 19:01:38 UTC
Created attachment 826244 [details]
File: cgroup

Comment 3 Martin Meyer 2013-11-19 19:01:41 UTC
Created attachment 826245 [details]
File: core_backtrace

Comment 4 Martin Meyer 2013-11-19 19:01:44 UTC
Created attachment 826246 [details]
File: dso_list

Comment 5 Martin Meyer 2013-11-19 19:01:47 UTC
Created attachment 826247 [details]
File: environ

Comment 6 Martin Meyer 2013-11-19 19:01:50 UTC
Created attachment 826248 [details]
File: limits

Comment 7 Martin Meyer 2013-11-19 19:01:53 UTC
Created attachment 826249 [details]
File: maps

Comment 8 Martin Meyer 2013-11-19 19:01:56 UTC
Created attachment 826250 [details]
File: open_fds

Comment 9 Martin Meyer 2013-11-19 19:01:59 UTC
Created attachment 826251 [details]
File: proc_pid_status

Comment 10 Fedora End Of Life 2015-05-29 09:48:40 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 11 Fedora End Of Life 2015-06-29 13:02:37 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.