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_type_check_instance_is_a executable: /usr/libexec/tracker-miner-fs kernel: 3.11.3-301.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 var_log_messages: Oct 4 13:33:10 localhost abrt[18901]: 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) Truncated backtrace: 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] File: backtrace
Created attachment 808016 [details] File: cgroup
Created attachment 808017 [details] File: core_backtrace
Created attachment 808018 [details] File: dso_list
Created attachment 808019 [details] File: environ
Created attachment 808020 [details] File: exploitable
Created attachment 808021 [details] File: limits
Created attachment 808022 [details] File: maps
Created attachment 808023 [details] File: open_fds
Created attachment 808024 [details] File: proc_pid_status
unknown. just happened to notice the problem notification reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_type_check_instance_is_a executable: /usr/libexec/tracker-miner-fs kernel: 3.11.10-301.fc20.x86_64 package: tracker-0.16.4-2.fc20 reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Copying a great amount of documents (LibreoOffice, etc...) from an external drive to my internal drive using Nautilus. reporter: libreport-2.1.10 abrt_installed_version: abrt-2.1.10-1.fc20.x86_64 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_type_check_instance_is_a executable: /usr/libexec/tracker-miner-fs kernel: 3.12.5-302.fc20.x86_64 libreport_version: libreport-2.1.10-1.fc20.x86_64 package: tracker-0.16.4-2.fc20 reason: tracker-miner-fs killed by SIGSEGV runlevel: N 5 satyr_version: satyr-0.12-1.fc20.x86_64 type: CCpp uid: 1000
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' 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.
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.