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 659569 - Removable devices should always be crawled when inserted
Removable devices should always be crawled when inserted
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: Miners
git master
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks: 728751
 
 
Reported: 2011-09-20 11:09 UTC by Sam Thursfield
Modified: 2021-05-26 22:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sam Thursfield 2011-09-20 11:09:39 UTC
If there is no crawl of the FS due (based on crawling-interval) then removable devices don't get crawled when inserted either:

Tracker-Message: Mount point added for URN 'urn:nepomuk:datasource:2E10-DC48'
Tracker-Message:   Adding directories in removable/optical media to crawler's queue
Tracker-Message:   Adding removable/optical: '/media/C3174946'
Tracker-Message: Crawling is disabled, waiting for DBus events

This seems wrong, since the files on the device may have changed, and now that we have removable device indexing disabled by default I don't see any performance arguments against this either.
Comment 1 Martyn Russell 2011-09-21 09:37:33 UTC
Interesting bug.

This boils down to which option has precedence AFAICS. Crawling interval configuration vs index removable devices.

My personal feeling is that disabling crawling interval (i.e. a setting of -2) should take priority over indexing removable devices. If I want to disable all crawling, I certainly don't want anything to happen when I insert media to my computer. On the other hand, if the crawling interval is > -2, then I think you're right.

This also highlights another issue in the tracker-preferences, that there is no link between the crawling interval option and the index removable devices option. So that needs fixing. There also isn't support for the crawling interval values of -1 vs > -1 cases either right now and that should be fixed too.
Comment 2 Sam Thursfield 2014-07-31 09:06:31 UTC
The IndexFileForProcess call in https://bugzilla.gnome.org/show_bug.cgi?id=680834 could mitigate this bug, if all apps interested in content were able to trigger crawling the USB device manually
Comment 3 Sam Thursfield 2021-05-26 22:26:33 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/tracker/-/issues/

Thank you for your understanding and your help.