https://bugs.kde.org/show_bug.cgi?id=439346
--- Comment #5 from skierpage <skierp...@gmail.com> --- (In reply to tagwerk19 from comment #2) > This is somehow a regression (as there wasn't an issue F33). If I remove the > X-systemd-skip line, baloo starts up OK. Yes I think that's it, so I was probably wrong to mention this baloo_file issue in systemd issue 18791. KDE commit 048edc5d2b29ea77d4e4226528e42031aac1c59a added the X-systemd-skip=true line: > Author: Henri Chain <henri.ch...@enioka.com> > Date: Thu Oct 15 09:21:09 2020 +0200 > Fix baloo_file autostart with systemd > Makes baloo_file started by systemd when systemd boot is enabled. > Disables auto generation of a service file by recent systemd > Will need to add `Wants=kde-baloo.service` to `plasma-workspace@.target` But this last bit is not in plasma-workspace.git's startkde/systemd/plasma-workspace@.target file, yet, so I tried it. I reverted to the original /etc/xdg/autostart/baloo_file.desktop and made the suggested change to /usr/lib/systemd/user/plasma-workspace@.target and rebooted, and kde-baloo.service started fine 👍. The previously generated /run/user/1000/systemd/generator.late/app-baloo_file@autostart.service is different from /usr/lib/systemd/user/kde-baloo.service (see attachment), the former has different settings, e.g. Restart=no, a different Slice name, and the extra ExecCondition=/usr/lib/systemd/systemd-xdg-autostart-condition "KDE:GNOME:Unity:XFCE" "" I'm no expert in grokking systemctl trees to tell if these are significant and belong in /usr/lib/systemd/user/kde-baloo.service. -- You are receiving this mail because: You are watching all bug changes.
