*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When searching using baloo6, the search indexer does nothing. Purge does nothing, disabling does nothing, enabling does nothing. When checking the status, the file indexer returns "Baloo Index could not be opened." Monitoring shows the program is doing nothing. This is incredibly frustrating, as there is seemingly no cause as the program is too cryptic to understand. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx System Version: Type1ProductConfigId
(In reply to Ethan J from comment #0) > ... When checking the status, the file indexer returns "Baloo Index could not be opened." The database file should be under .local/share/baloo, there should be an "index" and likely an "index-lock". Baloo needs to be able to create them (if they don't exist) and open them for writing. That's probably the first thing to check.
(In reply to tagwerk19 from comment #1) > ... That's probably the first thing to check ... Did you have any luck here? I assume this is a straightforward Fedora 40 (and not a silverblue immutable install)
(In reply to tagwerk19 from comment #2) > (In reply to tagwerk19 from comment #1) > > ... That's probably the first thing to check ... > Did you have any luck here? > > I assume this is a straightforward Fedora 40 (and not a silverblue immutable > install) The files do not exist in the directory.
(In reply to Ethan J from comment #3) > The files do not exist in the directory. Ok, I think I can duplicate the behaviour. On a clean Fedora 40, I disabled Baloo, checked the status, purged the index, checked the status and enabled Baloo again. So: test@fedora:~/.local/share/baloo$ balooctl6 disable Disabling and stopping the File Indexer test@fedora:~/.local/share/baloo$ balooctl6 status Baloo is currently disabled. To enable, please run balooctl enable test@fedora:~/.local/share/baloo$ balooctl6 purge Deleted the index database test@fedora:~/.local/share/baloo$ balooctl6 status Baloo is currently disabled. To enable, please run balooctl enable test@fedora:~/.local/share/baloo$ balooctl6 enable Baloo File Indexing has been disabled Enabling and starting the File Indexer test@fedora:~/.local/share/baloo$ balooctl6 status Baloo Index could not be opened This is where you are? Repeat the "balooctl6 enable" test@fedora:~/.local/share/baloo$ balooctl6 enable Enabling and starting the File Indexer test@fedora:~/.local/share/baloo$ balooctl6 status Baloo File Indexer is running Indexer state: Idle (Powersave) Total files indexed: 0 Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is 12.00 KiB This looks like Bug 435315
I have tried the sequence of commands shown, and it still says that Baloo Index could not be opened. Oddly enough, it is finding select files when I search from krunner.
(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)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to tagwerk19 from comment #6) > (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) I'm not sure what's going on here, but there is no systemctl service called kde-baloo.service on my computer. There is, however, a service called plasma-baloorunner.service. Upon listing its status, I get the following > Jul 29 17:30:49 Shlambak systemd[1818]: Starting plasma-baloorunner.service - KRunner provider for baloo file indexer... > Jul 29 17:30:50 Shlambak systemd[1818]: Started plasma-baloorunner.service - KRunner provider for baloo file indexer. > Jul 29 17:31:27 Shlambak baloorunner[40525]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched > Jul 29 17:31:27 Shlambak baloorunner[40525]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched > Jul 29 17:31:27 Shlambak baloorunner[40525]: qt.dbus.integration: Could not find slot Krunner1Adaptor::Teardown I don't know what the problem could be. I presume it could have something to do with switching from Plasma 5 to 6, but I'm not sure.
I'm not sure what is going on here. Could this be a fedora thing?
(In reply to Ethan J from comment #9) > I'm not sure what is going on here. Could this be a fedora thing? It appears to be a Fedora thing, as other Fedora users are having this issue. I'll transfer the bug over there.
(In reply to Ethan J from comment #10) > ... It appears to be a Fedora thing, as other Fedora users are having this > issue. I'll transfer the bug over there ... If you have any bug reports - anything on https://bugzilla.redhat.com I suppose - they would be interesting to see... I did try to reproduce on Fedora 40 (comment 4, comment 5) but I didn't find anything solid
It's way old, but maybe Bug 364042 is worth a look