Description of problem: For a while, baloo_file does not start when I boot Fedora 34. Version-Release number of selected component (if applicable): 5.83 How reproducible: Every time Steps to Reproduce: 1. Restart Fedora 2. balooctl status Actual results: "Baloo File Indexer is not running" There are no errors in journalctl. Expected results: baloo_file should start. Settings > File Search, Enable File Search is checked, my ~/.config/baloorc has Indexing-Enabled=true Additional info: I have /etc/xdg/autostart/baloo_file.desktop , it seems that should be enough for it to start. `/usr/libexec/kf5/klauncher /etc/xdg/autostart/baloo_file.desktop` fails with klauncher: This program is not supposed to be started manually. klauncher: It is started automatically by kdeinit5. But not for me. I also have a /usr/lib/systemd/user/kde-baloo.service , but `systemctl start kde-baloo.service` fails with Failed to start kde-baloo.service: Unit kde-baloo.service not found. One workaround is to uncheck [Enable File Search], [Apply], then check it and [Apply.
FYI, to check via systemctl what you want is: systemctl --user status kde-baloo or systemctl --user start kde-baloo (since it's a user unit, not a system one) But, alas I can reproduce here (it's not started automatically). Appears to be some sort of upstream issue.
(In reply to Rex Dieter from comment #1) > FYI, to check via systemctl what you want is: > systemctl --user status kde-baloo Thanks! user unit, makes sense. % systemctl --user status kde-baloo ○ kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; vendor preset: disabled) Active: inactive (dead) and `systemctl --user start kde-baloo` starts it fine. However, /etc/xdg/autostart/baloo_file.desktop has the line X-systemd-skip=true and if I start baloo_file by disabling and enabling from System Settings > File Search, systemctl thinks it's inactive. So it seems KDE startup (kdeinit5?) is expected to launch it, not systemd. > Appears to be some sort of upstream issue. I filed upstream bug https://bugs.kde.org/show_bug.cgi?id=439346
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This was fixed in KDE Plasma 5.23, the startkde/systemd/plasma-workspace@.target tried to start the wrong service name for Baloo.