Description of problem: tracker-store continually crashes/restarts after upgrade from F27->F29 Version-Release number of selected component (if applicable): Installed Packages mesa-libxatracker.x86_64 18.2.6-3.fc29 @System tracker.x86_64 2.1.5-2.fc29 @System tracker-miners.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot system Actual results: Dec 27 15:13:27 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager. Dec 27 15:13:27 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager... Dec 27 15:13:27 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager. Dec 27 15:13:29 t460.festive.local tracker-store[13071]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily relate d): No such file or directory) Dec 27 15:13:29 t460.festive.local systemd[1857]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE Dec 27 15:13:29 t460.festive.local systemd[1857]: tracker-store.service: Failed with result 'exit-code'. Dec 27 15:13:30 t460.festive.local systemd[1857]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart. Dec 27 15:13:30 t460.festive.local systemd[1857]: tracker-store.service: Scheduled restart job, restart counter is at 4945. Dec 27 15:13:30 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager. Dec 27 15:13:30 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager... Dec 27 15:13:30 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager. Dec 27 15:13:32 t460.festive.local tracker-store[13109]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily relate d): No such file or directory) Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Failed with result 'exit-code'. Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Service RestartSec=100ms expired, scheduling restart. Dec 27 15:13:32 t460.festive.local systemd[1857]: tracker-store.service: Scheduled restart job, restart counter is at 4946. Dec 27 15:13:32 t460.festive.local systemd[1857]: Stopped Tracker metadata database store and lookup manager. Dec 27 15:13:32 t460.festive.local systemd[1857]: Starting Tracker metadata database store and lookup manager... Dec 27 15:13:32 t460.festive.local systemd[1857]: Started Tracker metadata database store and lookup manager. Expected results: not this. Additional info: https://ask.fedoraproject.org/en/question/9822/how-do-i-disable-tracker-in-gnome/ Tried disabling search and the gsettings and neither stopped the crash looping. Also tried `tracker daemon stop` to no avail. looks like I finally had to "tracker reset -r -c" to get it to stop after having tried all the other things.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.