Also: It doesn’t ship with amanpage because KDE developers document it in online resources and help output (balooctl --help), not in traditional manpages.
That’s like typing ‘ls’ and then doing ‘man l’ and asking ‘why?’ when it’s broken…
> balooctl6 --help
Usage: balooctl6 [options] command status enable disable purge suspend resume check index clear config monitor indexSize failed
Options:
-f, --format <format> Output format <multiline|json|simple>.
The default format is "multiline".
Only applies to "balooctl status <file>"
-v, --version Displays version information.
-h, --help Displays help on commandline options.
--help-all Displays help, including generic Qt options.
Arguments:
command The command to execute
status Print the status of the indexer
enable Enable the file indexer
disable Disable the file indexer
purge Remove the index database
suspend Suspend the file indexer
resume Resume the file indexer
check Check for any unindexed files and index them
index Index the specified files
clear Forget the specified files
config Modify the Baloo configuration
monitor Monitor the file indexer
indexSize Display the disk space used by index
failed Display files which could not be indexed
Go into File Search, set to ‘File Names Only’ and disable locations… especially Nextcloud.
I have never been at those locations and wonder why this all off sudden popups when I just want to get work done.
I tried to uninstall baloo cause I have never used it and see no need for it
$ sudo dnf remove kf6-baloo
[sudo] password for j:
Failed to resolve the transaction:
Problem: installed package plasma-workspace-6.6.3-1.fc43.x86_64 requires kf6-baloo, but none of the providers can be installed
- installed package plasma-desktop-6.6.3-1.fc43.x86_64 requires plasma-workspace, but none of the providers can be installed
- conflicting requests
- problem with installed package
Could you share the file OP-1 Manual.pdf, in a bug report.
Uninstall baloo is ok as a workaround but informing the devs and other users (that’s the purpose of the bug tracker) will allow to actually fix the issue…
I finished qualifying the bug (with a gdb trace when the process hangs), it seems like an issue in upstream poppler, but the file renders fine in okular, so that might not be it.
Thanks again for the bug report and the file, this makes the bug much easier to reproduce and eventually fix.