Bug 855562

Summary: [abrt] tracker-0.14.2-1.fc17: hide_log_handler: Process /usr/libexec/tracker-store was killed by signal 4 (SIGILL)
Product: [Fedora] Fedora Reporter: marroy <olij.2406>
Component: trackerAssignee: Deji Akingunola <dakingun>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dakingun
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:15ce20d6ee30c876dcf3e416d39fe13f2df5a21f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 23:06:53 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description marroy 2012-09-09 00:41:47 UTC
Version-Release number of selected component:
tracker-0.14.2-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-store
crash_function: hide_log_handler
kernel:         3.5.3-1.fc17.i686

truncated backtrace:
:Thread no. 1 (2 frames)
: #0 hide_log_handler at tracker-log.c
: #3 tracker_main_main at /home/martyn/Source/tracker/src/tracker-store/tracker-main.vala

Comment 1 marroy 2012-09-09 00:41:49 UTC
Created attachment 611098 [details]
File: core_backtrace

Comment 2 marroy 2012-09-09 00:41:51 UTC
Created attachment 611099 [details]
File: environ

Comment 3 marroy 2012-09-09 00:41:53 UTC
Created attachment 611100 [details]
File: backtrace

Comment 4 marroy 2012-09-09 00:41:55 UTC
Created attachment 611101 [details]
File: limits

Comment 5 marroy 2012-09-09 00:41:56 UTC
Created attachment 611102 [details]
File: cgroup

Comment 6 marroy 2012-09-09 00:41:58 UTC
Created attachment 611103 [details]
File: maps

Comment 7 marroy 2012-09-09 00:42:00 UTC
Created attachment 611104 [details]
File: dso_list

Comment 8 marroy 2012-09-09 00:42:03 UTC
Created attachment 611105 [details]
File: var_log_messages

Comment 9 marroy 2012-09-09 00:42:05 UTC
Created attachment 611106 [details]
File: open_fds

Comment 10 Fedora End Of Life 2013-07-03 21:45:01 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 2013-07-31 23:06:57 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.