Summary: | Disabling, purging and re-enabling baloo search fails. | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | tagwerk19 |
Component: | balooctl | Assignee: | Stefan Brüns <stefan.bruens> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | bugseforuns, nate |
Priority: | NOR | ||
Version: | 5.69.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Write config changes back to disc |
Description
tagwerk19
2020-04-06 07:35:46 UTC
*** Bug 419989 has been marked as a duplicate of this bug. *** Don't run 'balooctl disable' before 'balooctl purge', purge does the right things by itself. Created attachment 127889 [details]
Write config changes back to disc
Here's a suggested patch that brings back the Frameworks 5.67 behaviour.
Tested with Neon Developer Edition and build with
sudo apt install liblmdb-dev
sudo apt install python-virtualenv
mkdir ~/baloo-env
cd ~/baloo-env
git clone git://anongit.kde.org/baloo
cmake baloo -DCMAKE_INSTALL_PREFIX=~/baloo-env
make -j4
It looks as if the indexing configuration was changed but the change was not written back to disc before the indexer was run.
Hope this helps. Thanks for baloo!
Please submit patches to our code review site. For more information, please see https://community.kde.org/Get_Involved/development This website currently seems to have an issue with its sidebar menu; you need to scroll down to see the contents. |