Bug 1039490

Summary: [abrt] telepathy-logger-0.8.0-3.fc20: _g_log_abort: Process /usr/libexec/telepathy-logger was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Igor Gnatenko <ignatenko>
Component: telepathy-loggerAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: high    
Version: 20CC: bdpepple, debarshir, ignatenko
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/120f1eaaace239bf13173f7b6f4324cac5e07b3a
Whiteboard: abrt_hash:83e94f6c67b487ac42bee37312dea26a52c7bfe4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:26:38 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Igor Gnatenko 2013-12-09 09:19:17 UTC
Description of problem:
Connected to jabber conference

Version-Release number of selected component:
telepathy-logger-0.8.0-3.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-logger
crash_function: _g_log_abort
executable:     /usr/libexec/telepathy-logger
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 _tp_channel_contacts_handle_owners_changed at channel-contacts.c:736
 #6 _tp_cli_channel_interface_group_invoke_callback_for_handle_owners_changed_detailed at _gen/tp-cli-channel-body.h:3294
 #7 tp_proxy_signal_invocation_run at proxy-signals.c:268

Comment 1 Igor Gnatenko 2013-12-09 09:19:22 UTC
Created attachment 834249 [details]
File: backtrace

Comment 2 Igor Gnatenko 2013-12-09 09:19:26 UTC
Created attachment 834250 [details]
File: cgroup

Comment 3 Igor Gnatenko 2013-12-09 09:19:29 UTC
Created attachment 834251 [details]
File: core_backtrace

Comment 4 Igor Gnatenko 2013-12-09 09:19:31 UTC
Created attachment 834252 [details]
File: dso_list

Comment 5 Igor Gnatenko 2013-12-09 09:19:33 UTC
Created attachment 834253 [details]
File: environ

Comment 6 Igor Gnatenko 2013-12-09 09:19:35 UTC
Created attachment 834254 [details]
File: limits

Comment 7 Igor Gnatenko 2013-12-09 09:19:38 UTC
Created attachment 834255 [details]
File: maps

Comment 8 Igor Gnatenko 2013-12-09 09:19:40 UTC
Created attachment 834256 [details]
File: open_fds

Comment 9 Igor Gnatenko 2013-12-09 09:19:45 UTC
Created attachment 834258 [details]
File: proc_pid_status

Comment 10 Igor Gnatenko 2013-12-09 09:19:47 UTC
Created attachment 834259 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-05-29 09:56:51 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 12 Fedora End Of Life 2015-06-29 13:26:38 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.