Bug 1074702

Summary: [abrt] telepathy-haze: __pthread_mutex_lock(): telepathy-haze killed by SIGSEGV
Product: [Fedora] Fedora Reporter: ZiN <metanoite>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:df63e5966b5b6b916a0dc084b5e151a3b819f0fc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:23: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:
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
File: var_log_messages
none
File: exploitable none

Description ZiN 2014-03-10 22:16:53 UTC 
Description of problem:
Some telepathy subprocess crashes. Perhaps after some keepalive interval reconnection.

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

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-haze
crash_function: __pthread_mutex_lock
executable:     /usr/libexec/telepathy-haze
kernel:         3.12.9-301.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66
 #1 host_table_final at rpc/hosttable.c:54
 #2 my_fini at rpc/hosttable.c:79
 #3 _dl_close_worker at dl-close.c:272
 #4 _dl_close at dl-close.c:782
 #5 dlclose_doit at dlclose.c:35
 #6 _dl_catch_error at dl-error.c:177
 #7 _dlerror_run at dlerror.c:163
 #8 __dlclose at dlclose.c:46
 #9 _g_module_close at gmodule-dl.c:138
Comment 1 ZiN 2014-03-10 22:16:56 UTC 
Created attachment 872860 [details]
File: backtrace
Comment 2 ZiN 2014-03-10 22:16:58 UTC 
Created attachment 872861 [details]
File: cgroup
Comment 3 ZiN 2014-03-10 22:17:01 UTC 
Created attachment 872862 [details]
File: core_backtrace
Comment 4 ZiN 2014-03-10 22:17:03 UTC 
Created attachment 872863 [details]
File: dso_list
Comment 5 ZiN 2014-03-10 22:17:05 UTC 
Created attachment 872864 [details]
File: environ
Comment 6 ZiN 2014-03-10 22:17:07 UTC 
Created attachment 872865 [details]
File: limits
Comment 7 ZiN 2014-03-10 22:17:10 UTC 
Created attachment 872866 [details]
File: maps
Comment 8 ZiN 2014-03-10 22:17:12 UTC 
Created attachment 872867 [details]
File: open_fds
Comment 9 ZiN 2014-03-10 22:17:14 UTC 
Created attachment 872868 [details]
File: proc_pid_status
Comment 10 ZiN 2014-03-10 22:17:16 UTC 
Created attachment 872869 [details]
File: var_log_messages
Comment 11 ZiN 2014-03-10 22:17:18 UTC 
Created attachment 872870 [details]
File: exploitable
Comment 12 Fedora End Of Life 2015-05-29 11:13:05 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 13 Fedora End Of Life 2015-06-29 19:23:58 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.