Red Hat Bugzilla – Bug 1015735
[abrt] tracker-0.16.2-4.fc20: g_type_check_instance_is_a: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:33:15 EDT
Version-Release number of selected component:
var_log_messages: Oct 4 13:33:10 localhost abrt: Saved core dump of pid 1790 (/usr/libexec/tracker-miner-fs) to /var/tmp/abrt/ccpp-2013-10-04-13:33:09-1790 (118071296 bytes)
Thread no. 1 (6 frames)
#0 g_type_check_instance_is_a at gtype.c:3975
#1 g_file_get_child at gfile.c:770
#2 file_enumerate_next_cb at tracker-crawler.c:736
#3 next_async_callback_wrapper at gfileenumerator.c:306
#4 g_task_return_now at gtask.c:1108
#5 complete_in_idle_cb at gtask.c:1117
Potential duplicate: bug 817318
Created attachment 808015 [details]
Created attachment 808016 [details]
Created attachment 808017 [details]
Created attachment 808018 [details]
Created attachment 808019 [details]
Created attachment 808020 [details]
Created attachment 808021 [details]
Created attachment 808022 [details]
Created attachment 808023 [details]
Created attachment 808024 [details]
unknown. just happened to notice the problem notification
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
runlevel: N 5
Another user experienced a similar problem:
Copying a great amount of documents (LibreoOffice, etc...) from an external drive to my internal drive using Nautilus.
reason: tracker-miner-fs killed by SIGSEGV
runlevel: N 5
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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'
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.