Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (6 frames)
#0 g_type_check_instance_is_a at gtype.c:3999
#1 g_file_get_child at gfile.c:722
#2 file_enumerate_next_cb at tracker-crawler.c:736
#3 next_async_callback_wrapper at gfileenumerator.c:297
#4 g_task_return_now at gtask.c:1105
#5 complete_in_idle_cb at gtask.c:1114
Potential duplicate: bug 817318
Created attachment 758578 [details]
Created attachment 758579 [details]
Created attachment 758580 [details]
Created attachment 758581 [details]
Created attachment 758582 [details]
Created attachment 758583 [details]
Created attachment 758584 [details]
Created attachment 758585 [details]
Created attachment 758586 [details]
Created attachment 758587 [details]
i think it was while moving a couple of thousand files from an ntfs system.
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
runlevel: N 5
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
tracker-0.16.4-4.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tracker-0.16.4-4.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
*** Bug 990954 has been marked as a duplicate of this bug. ***
tracker-0.16.5-1.fc20 has been submitted as an update for Fedora 20.
tracker-0.16.5-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 973850 has been marked as a duplicate of this bug. ***