Description of problem: The miner crashes every time after gnome-shell starts. Version-Release number of selected component: tracker-miners-2.0.3-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_pattern_match executable: /usr/libexec/tracker-miner-fs journald_cursor: s=ab0a884199d84b75b6e92095edd871f3;i=daae;b=5d6901352f2945628055d893ec665b8e;m=1caac6760;t=55f94e541b2e1;x=5914a0fc37b76b2f kernel: 4.13.16-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1363156 [details] File: backtrace
Created attachment 1363157 [details] File: cgroup
Created attachment 1363158 [details] File: core_backtrace
Created attachment 1363159 [details] File: cpuinfo
Created attachment 1363160 [details] File: dso_list
Created attachment 1363161 [details] File: environ
Created attachment 1363162 [details] File: limits
Created attachment 1363163 [details] File: maps
Created attachment 1363164 [details] File: mountinfo
Created attachment 1363165 [details] File: open_fds
Created attachment 1363166 [details] File: proc_pid_status
Confirmed also on my Fedora 27 Workstation, everytime i login in gnome-shell, it throws this error ABRT: https://retrace.fedoraproject.org/faf/reports/bthash/668761a3be59c62bac1f33ea65e9a4c085c67c1a
Issue Solved by deleting tor-browser folder i had on my Desktop (downloaded to try it and used few times. from https://www.torproject.org/projects/torbrowser.html.en) Probably other people affected by this bug can check if they have the tor-browser folder. Maybe some files in it makes tracker to crash...
*** Bug 1570234 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happened after coming back from a gnome-shell crash, happens this way a few times a week currently. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_pattern_match executable: /usr/libexec/tracker-miner-fs journald_cursor: s=00e863d4809648d6bc5145f9b1c9eea0;i=31293;b=45a32a3dc5f34f1d9ad04f0675a6753f;m=687f60360;t=56bfad073e476;x=8bd7022053030a59 kernel: 4.16.6-202.fc27.x86_64 package: tracker-miners-2.0.4-2.fc27 reason: tracker-miner-fs killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Greater than 50% of the time when I return from a suspend or locked screen, first gnome-shell crashes, then tracker-miner-fs crashes right afterward. That is what happened this time. Sometimes tracker-miner-fs crashes without gnome-shell crashing first. This is an F27 install where I moved my ~/ from CentOS 7, and the same ~/ has been following me around for a while. There is a chance I have an old config file crossing paths; if you have suggestions on which ones to experiment moving out of the way (so new ones get created, etc.), I am willing to try. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_pattern_match executable: /usr/libexec/tracker-miner-fs journald_cursor: s=e677ef8f1d224b8e859e5d630ef737fe;i=6b01b;b=9a72579ac8e645e0befabcd0f4d2639d;m=4a264960dd;t=56e9d300860b5;x=1ac805b92bef9743 kernel: 4.16.12-200.fc27.x86_64 package: tracker-miners-2.0.4-2.fc27 reason: tracker-miner-fs killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
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.