Commits on Source (11)
-
Carlos Garnacho authored
This might be called in the right circumstances that the current_dir is NULL, cater for that. Fixes possible warnings like: tracker-miner-f[2965]: g_file_equal: assertion 'G_IS_FILE (file1)' failed tracker-miner-f[2965]: g_file_has_prefix: assertion 'G_IS_FILE (file)' failed (cherry-picked from commit 5a052219) Closes: https://gitlab.gnome.org/GNOME/tracker/-/issues/342
9f2be3db -
Carlos Garnacho authored
libtracker-miner: Fix possible warnings [3.4] See merge request https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/426
fcdb9838 -
Nart Tlisha authored66164e67
-
Carlos Garnacho authored
In the case of a btrfs partition with multiple subvolumes, we will create the stable identifiers based on the mountpoint device name, this falls short if multiple mountpoint entries exist for the same partition and different subvolumes. Make the subvolume name part of the stable identifier, so that we can distinguish between subvolumes of a single partition.
5caea532 -
Carlos Garnacho authored
We would mistakenly resort to the parent mountpoint identifier, instead of the one belonging to the directory itself.
88e1c7fb -
Carlos Garnacho authored
If the stable identifier changes for a folder, we may end up with stale nie:interpretedAs links to it. Since we don't allow symlinks or other loops in the filesystem, it's safe to assume the nie:DataObject/nie:InformationElement will be 1:1 for folders.
7e401819 -
Carlos Garnacho authored
Commit 2425ed05 attempted to drop fluidsynth GStreamer plugin which tries to access hardware devices during metadata extraction and triggers the seccomp jail. However the wrong name was pulled here, we should use the name of the plugin itself, not the decoder element. Fixes: 2425ed05 - tracker-extract: Avoid the fluiddec gstreamer plugin Closes: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/249
49d3a70e -
Carlos Garnacho authored
This is something only officially supported in meson >= 0.60, but we just require 0.51 here.
8ac109c7 -
Carlos Garnacho authored
Since we are using g_*_source_new() API to attach the source to non-default main contexts, we cannot use g_source_remove() to remove its ID, but must g_source_destroy() the GSource to detach it from the main loop.
8be03a67 -
Carlos Garnacho authored83054c8c
-
Jeremy Bicha authored1759f849