After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 415957 - update results automatically if there are changes on monitored directories
update results automatically if there are changes on monitored directories
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: Needle
git master
Other All
: Normal enhancement
: ---
Assigned To: Jamie McCracken
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2007-03-08 04:57 UTC by Tshepang Lekhonkhobe
Modified: 2018-08-11 21:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tshepang Lekhonkhobe 2007-03-08 04:57:18 UTC
TST should continuously return fresh results as the filesystem changes instead of requiring user to run click Find again.
another note: After performing a search and then modifying one of the files that shows on the results, the entry disappears even if the changes have nothing to do with the search term (except share the same file).
Comment 1 Martyn Russell 2010-03-11 15:21:44 UTC
Can the reporter of this bug set the _version_ so we can target bugs to work on more easily please. We can also have an idea about if these bugs are likely to be obsolete too.

If you don't set the version, we are less likely to look at them.

Sorry for the spam, but I don't want to say this 88 times on each bug :)
Comment 2 Tshepang Lekhonkhobe 2010-05-27 17:55:15 UTC
updating the report:
TST should automatically refresh results whenever there are changes in tracker-store.
Comment 3 Ritesh Raj Sarraf 2015-11-27 09:07:02 UTC
Actually, I think this issue is still valid.

@Martyn Russell: Here's the detail you've asked.

rrs@learner:~$ dpkg -l | grep -i tracker
ii  gir1.2-tracker-1.0:amd64                  1.6.1-1                                amd64        GObject introspection data for Tracker
ii  libtracker-control-1.0-0:amd64            1.6.1-1                                amd64        library to control/monitor tracker miners
ii  libtracker-miner-1.0-0:amd64              1.6.1-1                                amd64        tracker data miner library
ii  libtracker-sparql-1.0-0:amd64             1.6.1-1                                amd64        metadata database, indexer and search tool - library
ii  libxatracker2:amd64                       11.0.5-1                               amd64        X acceleration library -- runtime
ii  rygel-tracker                             0.28.1-1                               amd64        GNOME UPnP/DLNA services - Tracker plugin
ii  tracker                                   1.6.1-1                                amd64        metadata database, indexer and search tool
ii  tracker-extract                           1.6.1-1                                amd64        metadata database, indexer and search tool - metadata extractors
ii  tracker-gui                               1.6.1-1                                amd64        metadata database, indexer and search tool - GNOME frontends
ii  tracker-miner-fs                          1.6.1-1                                amd64        metadata database, indexer and search tool - filesystem indexer
2015-11-27 / 14:33:27 ♒♒♒  ☺    




Given that tracker uses inotify, I'm wondering why the changes are not picked ?
Is it because of performance problems ?

If so, I think you still should provide users the functionality through GUI/CLI Interface, and let them choose.

Also, intofiy file changes should be tracked and put in a queue, to be processed later (like in if the user has requested the indexing to only happen when on AC)
Comment 4 Sam Thursfield 2018-08-11 21:45:26 UTC
Thanks for the feedback. tracker-needle (a.k.a tracker search tool) was discontinued in Tracker 2.0.0, so this is now obsolete.