Version-Release number of selected component: tracker-miners-2.0.2-1.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=0c32b52a012d4dd88df3ca02188c9c2d;i=89d4d;b=b820c711f05c488cb6eea68ac4c8874c;m=8217b1e9;t=55c2b34b575a9;x=4fba31092d6577bc kernel: 4.13.8-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 process_func_start at tracker-crawler.c:724 #1 enumerate_next_cb at tracker-crawler.c:941 #2 next_async_callback_wrapper at gfileenumerator.c:305 #3 g_task_return_now at gtask.c:1145 #4 complete_in_idle_cb at gtask.c:1159
Created attachment 1341892 [details] File: backtrace
Created attachment 1341893 [details] File: cgroup
Created attachment 1341894 [details] File: core_backtrace
Created attachment 1341895 [details] File: cpuinfo
Created attachment 1341896 [details] File: dso_list
Created attachment 1341897 [details] File: environ
Created attachment 1341898 [details] File: exploitable
Created attachment 1341899 [details] File: limits
Created attachment 1341900 [details] File: maps
Created attachment 1341901 [details] File: open_fds
Created attachment 1341902 [details] File: proc_pid_status
Created attachment 1341903 [details] File: var_log_messages
*** Bug 1528894 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The system seemed to run normally, and didn't notice anything out of the unusual reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=4d973911f492488891ed1177c6c28e71;i=babb;b=c714ea74c2bb484d8563c7e7649c8083;m=8229b33a56;t=56181de032c0f;x=b1eb95cd4596d681 kernel: 4.14.8-300.fc27.x86_64 machineid: systemd=092b753c6a7e448686e037395a7f8228 package: tracker-miners-2.0.3-1.fc27 reason: tracker-miner-fs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I unpacked 28 zip files using the following scripts: for x in ../*.zip ; do bc-unpack "$x" ; done ... #! /bin/bash set -e if [[ "$1" == "" ]] ; then exit 1 fi zip_file="$1" # unzip it original_directory="$(dtrx -v "$1" | head -1)" artist_name="$(echo "$original_directory" | sed -e "s: - .*::")" album_name="$(echo "$original_directory" | sed -e "s:.* - ::")" new_directory="$artist_name/$album_name" mkdir -p "$new_directory" mv "$original_directory"/* "$new_directory" rmdir "$original_directory" reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=5583550571934b76a562d5090547ff9a;i=1aa9f;b=446d952fcdcc4b59b5ee2193340c6c26;m=1536738366c;t=561fd343a765d;x=85d16ada8f0960ee kernel: 4.13.16-302.fc27.x86_64 package: tracker-miners-2.0.3-1.fc27 reason: tracker-miner-fs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1531943 has been marked as a duplicate of this bug. ***
*** Bug 1534115 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This problem happens when I was using Google Chrome and Terminal for compile Brackets to Fedora 27. Then system show me a pop-up with this error report. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=c147491512154215ad9000921801a7fa;i=6270;b=71e7c2d28fbb440fa724ccab3ea508f1;m=17c2a743a;t=5630cd2e9ccfc;x=10e6f087388688fa kernel: 4.14.13-300.fc27.x86_64 package: tracker-miners-2.0.3-1.fc27 reason: tracker-miner-fs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1539305 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Issue happened after removing the contents of a build directory and rerunning configure for the same package. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=b54edc2182684610bc4b0795f761d2dd;i=6dc81;b=cd267d8c8db64b8abbab8ac9f4aef1fa;m=14dc6f7e5;t=56527f74789bf;x=4115cb796fa1d8e8 kernel: 4.14.18-300.fc27.x86_64 package: tracker-miners-2.0.3-1.fc27 reason: tracker-miner-fs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: How I know what file cause indexer crash? reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: process_func_start executable: /usr/libexec/tracker-miner-fs journald_cursor: s=a5b07b9d31bd4be8ba071744ce975765;i=9343;b=e5a3578773804d45b18646e0829366c2;m=aadbaeb7d;t=566c0214dffe5;x=cc1278a9c48d07c kernel: 4.16.0-rc1-amd-vega+ package: tracker-miners-2.0.4-2.fc27 reason: tracker-miner-fs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1570087 has been marked as a duplicate of this bug. ***
*** Bug 1581604 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.