https://bugs.kde.org/show_bug.cgi?id=402154
Peter Hoeg <pe...@hoeg.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pe...@hoeg.com
--- Comment #47 from Peter Hoeg <pe...@hoeg.com> ---
This might be *slightly* off-topic, but here's a hacky workaround that I can
live until this is properly fixed.
1. run baloo as a systemd service which has been (io)niced as much as possible
2. use `ExecStartPre` to run a script that checks if the device id of
$HOME/.config has changed and if so, blow away the baloo index and rebuild.
This means that after most restarts, it will be about 20 minutes before
everything has been indexed, but that's totally acceptable (for me).
This is the script:
```
#!/usr/bin/env bash
set -eEuo pipefail
STAT_FILE=$XDG_CACHE_HOME/baloo.state
test -f $STAT_FILE || touch $STAT_FILE
if [ "$(stat --format='%Hd,%d' $HOME/.config)" != "$(cat $STAT_FILE)" ]; then
echo "Device number changed. Resetting baloo index"
balooctl suspend
balooctl disable
pkill -9 baloo_file || true
balooctl purge
balooctl enable
balooctl suspend
stat --format='%Hd,%d' $HOME/.config > $STAT_FILE
fi
# in case it was started outside systemd
pkill -9 baloo_file || true
```
--
You are receiving this mail because:
You are watching all bug changes.
