https://bugs.kde.org/show_bug.cgi?id=526391
Bug ID: 526391
Summary: Baloo refuses to index FUSE network mounts (e.g.
rclone), with no opt-in override
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Baloo excludes FUSE-based network filesystems from indexing, with no way to
override it, and no error message indicating this is happening. This affects
filename indexing, not just content. The folder shows as configured correctly,
but is never actually crawled, with no error anywhere. (Except the "Not
running, 0% complete" message in System Settings.)
Environment: rclone mount of a Box.com remote, filesystem type reported as
fuse.rclone per the logs.
Steps to reproduce:
- Mount a remote: rclone mount remote:path /local/mountpoint
- balooctl config add includeFolders /local/mountpoint
- balooctl config set contentIndexing false (to rule out content extraction as
a variable)
- balooctl check, restart kde-baloo.service
- Wait (in my case, several days)
Expected: Baloo crawls and indexes the folder's filenames.
Actual:
- System Settings shows the folder as "Not running, 0% complete" indefinitely.
- balooctl status file count does not move.
- Real tree size, via rclone lsjson -R --fast-list, is 200,000+ entries; Baloo
never approaches this.
- baloosearch6 finds nothing for untouched files deep in the tree, confirming
the index itself is empty there.
- Dolphin/KRunner do eventually return results, but that's a separate live
filesystem crawl, not Baloo's index.
- With debug logging on, kde-baloo.service explicitly logs the mount by type at
startup: Adding "fuse.rclone/home/craig/production/Media Loft Box" type:
"fuse.rclone"
This points to the StorageDevices/removable-media gating mechanism, separate
from includeFolders/excludeFolders and not exposed anywhere in baloofilerc or
balooctl config.
This is likely intended behavior from bug 343437 ("Do not Index NFS," RESOLVED
FIXED), where indexing network shares was deliberately disabled after it
overloaded a shared NFS server. Reasonable default for that case.
The request then, I suppose, would be to add an explicit opt-in override, a
config key or per-folder toggle, letting a user index a specific folder despite
its network/FUSE classification, for cases like a personal single-user mount
where the original NFS server-load concern doesn't apply. "Please index the
folder I explicitly asked you to index." is a pretty reasonable task for a file
indexer.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.7-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × Intel® Core™ Ultra 9 285K
Memory: 32 GiB of RAM (30.7 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 5070 Ti
Graphics Processor 2: Intel® Graphics
--
You are receiving this mail because:
You are watching all bug changes.
