Bug 1021421

Summary: [abrt] telepathy-haze-0.8.0-1.fc20: g_hash_table_lookup_node: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jakub Hrozek <jhrozek>
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, elreydetodo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c8cb1c1075d13fd97b37fa43679017cd7e4f0bdd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:40:51 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 Jakub Hrozek 2013-10-21 09:29:35 UTC 
Description of problem:
I have no idea how to reproduce the problem. The computer was docked and network was available.

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

Additional info:
reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-haze
crash_function: g_hash_table_lookup_node
executable:     /usr/libexec/telepathy-haze
kernel:         3.11.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            10327

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 g_hash_table_lookup_node at ghash.c:365
 #2 g_hash_table_lookup at ghash.c:1076
 #3 tp_asv_get_string at dbus.c:987
 #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

Potential duplicate: bug 977400
Comment 1 Jakub Hrozek 2013-10-21 09:29:39 UTC 
Created attachment 814493 [details]
File: backtrace
Comment 2 Jakub Hrozek 2013-10-21 09:29:42 UTC 
Created attachment 814494 [details]
File: cgroup
Comment 3 Jakub Hrozek 2013-10-21 09:29:46 UTC 
Created attachment 814495 [details]
File: core_backtrace
Comment 4 Jakub Hrozek 2013-10-21 09:29:49 UTC 
Created attachment 814496 [details]
File: dso_list
Comment 5 Jakub Hrozek 2013-10-21 09:29:52 UTC 
Created attachment 814497 [details]
File: environ
Comment 6 Jakub Hrozek 2013-10-21 09:29:56 UTC 
Created attachment 814498 [details]
File: exploitable
Comment 7 Jakub Hrozek 2013-10-21 09:29:59 UTC 
Created attachment 814499 [details]
File: limits
Comment 8 Jakub Hrozek 2013-10-21 09:30:02 UTC 
Created attachment 814500 [details]
File: maps
Comment 9 Jakub Hrozek 2013-10-21 09:30:07 UTC 
Created attachment 814501 [details]
File: open_fds
Comment 10 Jakub Hrozek 2013-10-21 09:30:10 UTC 
Created attachment 814503 [details]
File: proc_pid_status
Comment 11 Jakub Hrozek 2013-10-21 09:30:13 UTC 
Created attachment 814504 [details]
File: var_log_messages
Comment 12 Martin Meyer 2013-12-18 16:21:14 UTC 
This seg fault is related to bug 1025506, which is happening several times a day. Various parts of g-o-a are constantly crashing for me, and bug 1031662 is the final part where I open online accounts in control center and everything restarts.

Please, someone help me to debug this situation. It's making me very sad. I never get IMs on my desktop at work :'(
Comment 13 Fedora End Of Life 2015-05-29 09:36: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 14 Fedora End Of Life 2015-06-29 12:40:51 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.