https://bugs.kde.org/show_bug.cgi?id=439346
Bug ID: 439346
Summary: baloo_file doesn't start when desktop plasma starts
Product: frameworks-baloo
Version: 5.83.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: baloo-bugs-n...@kde.org
Reporter: skierp...@gmail.com
Target Milestone: ---
SUMMARY
For a while, baloo_file does not start when I boot Fedora 34.
STEPS TO REPRODUCE
1. Restart Fedora
2. balooctl status
OBSERVED RESULT
"Baloo File Indexer is not running"
There are no errors in journalctl.
EXPECTED RESULT
baloo_file should start. System Settings > File Search, Enable File Search is
checked, my ~/.config/baloorc has Indexing-Enabled=true
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2 on Wayland
ADDITIONAL INFORMATION
I initially filed Fedora bug
https://bugzilla.redhat.com/show_bug.cgi?id=1977594 , Rex Dieter reproduced it
and commented
> But, alas I can reproduce here (it's not started automatically). Appears
> to be some sort of upstream issue.
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 don't know how to debug KDE startup.
One workaround is run System Settings > File Search, uncheck [Enable File
Search], [Apply], then check it and [Apply].
I also have a /usr/lib/systemd/user/kde-baloo.service , but starting Baloo as
above does not make it show up in `systemctl --user status kde-baloo`, so KDE
on Fedora is not using this systemd unit. `systemctl --user start
kde-baloo.service` is another workaround.
--
You are receiving this mail because:
You are watching all bug changes.
