Red Hat Bugzilla – Bug 961918
[abrt] tracker-0.16.1-1.fc19: g_file_get_child: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Last modified: 2014-07-27 10:26:36 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (5 frames)
#0 g_file_get_child at gfile.c:722
#1 file_enumerate_next_cb at tracker-crawler.c:736
#2 next_async_callback_wrapper at gfileenumerator.c:297
#3 g_task_return_now at gtask.c:1105
#4 complete_in_idle_cb at gtask.c:1114
Potential duplicate: bug 820055
Created attachment 746304 [details]
Created attachment 746305 [details]
Created attachment 746306 [details]
Created attachment 746307 [details]
Created attachment 746308 [details]
Created attachment 746309 [details]
Created attachment 746310 [details]
Created attachment 746311 [details]
Created attachment 746312 [details]
Created attachment 746313 [details]
I was "Extract here" a zip file when this happened.
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
runlevel: N 5
And it happened again after a restart.
I just got this also, according to abrt.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
thank you for this bug. Now we have in repos 1.0.2 so I think you can't reproduce this bug. If you can - please re-open!
In which repos? I yum updated my F20 just last night and I still have:
This mirror: http://fedora.mirror.nexicom.net/linux/updates/20/x86_64/?C=M;O=D currently shows no new tracker packages in it and this bug is still well and alive in the current 0.16.4 release IIRC.
Please reopen this bug until it actually is closed in the current *production* release. Having it closed in a development release does nobody (except developers) any good.