https://bugs.kde.org/show_bug.cgi?id=489584
--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to Ethan J from comment #5)
> I have tried the sequence of commands shown, and it still says that Baloo
> Index could not be opened.
You probably don't have any debugging set up, let's try that first.
Create a folder, ~/config/QtProject, and a file
~/config/QtProject/qtlogging.ini
Edit the qtlogging.ini so that includes:
[Rules]
kf.baloo=true;
kf.baloo.*=true;
Restart (with systemctl --user start kde-baloo.service) and see that you get in
the journal (try systemctl --user status kde-baloo.service). I get:
Jul 14 07:29:41 fedora systemd[1019]: Starting kde-baloo.service - Baloo
File Indexer Daemon...
Jul 14 07:29:41 fedora systemd[1019]: Started kde-baloo.service - Baloo
File Indexer Daemon.
Jul 14 07:29:41 fedora baloo_file[3523]: Failed to create database,
removing corrupted database.
Jul 14 07:29:41 fedora baloo_file[3523]: Failed to create database after
deleting corrupted one.
Jul 14 07:29:41 fedora systemd[1019]: kde-baloo.service: Main process
exited, code=exited, status=1/FAILURE
Jul 14 07:29:41 fedora systemd[1019]: kde-baloo.service: Failed with result
'exit-code'.
If baloo cannot create a "~/.local/share/baloo" directory or
Jul 14 07:44:34 fedora systemd[1019]: Starting kde-baloo.service - Baloo
File Indexer Daemon...
Jul 14 07:44:34 fedora systemd[1019]: Started kde-baloo.service - Baloo
File Indexer Daemon.
Jul 14 07:44:34 fedora baloo_file[5252]: kf.baloo.engine:
"/home/webfeet/.local/share/baloo" does not have write permissions. Aborting
Jul 14 07:44:34 fedora baloo_file[5252]: Failed to create database,
removing corrupted database.
Jul 14 07:44:34 fedora baloo_file[5252]: kf.baloo.engine:
"/home/webfeet/.local/share/baloo" does not have write permissions. Aborting
Jul 14 07:44:34 fedora baloo_file[5252]: Failed to create database after
deleting corrupted one.
If Baloo cannot write into the folder.
> ... Oddly enough, it is finding select files when I search from krunner ...
Which is indeed strange, it is not just "recent files", you get the results
from a file search?
That sounds like krunner is able to find and read an index even if the indexer
is not able to find it and write to it... (I am assuming that the results you
get from krunner are old)
--
You are receiving this mail because:
You are watching all bug changes.
