https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #31 from postix <pos...@posteo.eu> ---
So I've changed the entry in baloofilerc to meet the systemd script start
condition, enabled the service and rebooted:
```
> systemctl --user status kde-baloo.service
● kde-baloo.service - Baloo File Indexer Daemon
Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; enabled; preset:
disabled)
Active: active (running) since Tue 2025-02-25 13:22:23 CET; 14s ago
Invocation: 0cc65a24c82f47f2ac68e505c84f9945
Process: 2516 ExecCondition=/usr/bin/kde-systemd-start-condition
--condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited,
status=0/SUCCESS)
Main PID: 2519 (baloo_file)
Tasks: 3 (limit: 38234)
CPU: 328ms
CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
└─2519 /usr/libexec/baloo_file
systemd[2436]: Starting Baloo File Indexer Daemon...
systemd[2436]: Started Baloo File Indexer Daemon.
baloo_file[2519]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner ''
but we thought it was ':1.31'
baloo_file[2519]: QDBusConnection: name 'org.freedesktop.UPower' had owner ''
but we thought it was ':1.35'
```
--
You are receiving this mail because:
You are watching all bug changes.
