Bug 1017670

Summary: [abrt] tracker-0.16.2-4.fc20: g_file_get_child: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Carlos Morel-Riquelme <quantenselbstmord>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alex.qiu2012, Bengt.Lueers, dakingun, debarshir, juergen.sch, martinsson.patrik, plarsen, ravis, seweryn, vikigoyal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f4877f346acfe13ce2bb79c06007f7877469cd52
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:36:18 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Carlos Morel-Riquelme 2013-10-10 10:18:43 UTC 
Version-Release number of selected component:
tracker-0.16.2-4.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_file_get_child
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.11.1-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_file_get_child at gfile.c:770
 #1 file_enumerate_next_cb at tracker-crawler.c:736
 #2 next_async_callback_wrapper at gfileenumerator.c:306
 #3 g_task_return_now at gtask.c:1108
 #4 complete_in_idle_cb at gtask.c:1117

Potential duplicate: bug 820055
Comment 1 Carlos Morel-Riquelme 2013-10-10 10:18:47 UTC 
Created attachment 810427 [details]
File: backtrace
Comment 2 Carlos Morel-Riquelme 2013-10-10 10:18:50 UTC 
Created attachment 810428 [details]
File: cgroup
Comment 3 Carlos Morel-Riquelme 2013-10-10 10:18:54 UTC 
Created attachment 810429 [details]
File: core_backtrace
Comment 4 Carlos Morel-Riquelme 2013-10-10 10:18:58 UTC 
Created attachment 810430 [details]
File: dso_list
Comment 5 Carlos Morel-Riquelme 2013-10-10 10:19:01 UTC 
Created attachment 810431 [details]
File: environ
Comment 6 Carlos Morel-Riquelme 2013-10-10 10:19:04 UTC 
Created attachment 810432 [details]
File: exploitable
Comment 7 Carlos Morel-Riquelme 2013-10-10 10:19:07 UTC 
Created attachment 810433 [details]
File: limits
Comment 8 Carlos Morel-Riquelme 2013-10-10 10:19:11 UTC 
Created attachment 810434 [details]
File: maps
Comment 9 Carlos Morel-Riquelme 2013-10-10 10:19:14 UTC 
Created attachment 810435 [details]
File: open_fds
Comment 10 Carlos Morel-Riquelme 2013-10-10 10:19:18 UTC 
Created attachment 810436 [details]
File: proc_pid_status
Comment 11 Peter Larsen 2014-02-07 01:26:54 UTC 
Just ran into the same issue (abrt identified this as a duplicate).
Comment 12 vikram goyal 2014-06-17 08:33:05 UTC 
Another user experienced a similar problem:

happened by itself

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: g_file_get_child
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.14.7-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGSEGV
runlevel:       1 5
type:           CCpp
uid:            1000
Comment 13 Fedora Admin XMLRPC Client 2014-07-26 17:12:30 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 14 Fedora Admin XMLRPC Client 2014-07-27 06:34:28 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 15 Fedora End Of Life 2015-05-29 09:32:57 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 16 Fedora End Of Life 2015-06-29 12:36:18 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.