https://bugs.kde.org/show_bug.cgi?id=419708
Bug ID: 419708
Summary: Disabling, purging and re-enabling baloo search fails.
Product: frameworks-baloo
Version: 5.69.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: balooctl
Assignee: stefan.bru...@rwth-aachen.de
Reporter: tagwer...@innerjoin.org
Target Milestone: ---
SUMMARY:
If baloo is disabled and the database purged, it needs to be reenabled
twice to restart indexing.
STEPS TO REPRODUCE:
Run
balooctl disable
balooctl purge
balooctl enable
balooctl status
OBSERVED RESULTS:
balooctl status says:
Baloo Index could not be opened
A concurrently running "balooctl monitor" saying:
Waiting for file indexer to start
Running "balooctl enable" a second time and repeating the "balooctl status"
gives:
Baloo File Indexer is running
Indexer state: Idle (Powersave)
Total files indexed: 0
Files waiting for content indexing: 0
Files failed to index: 0
EXPECTED RESULTS:
balooctl enable starts (or restart) the indexing
SOFTWARE/OS VERSIONS:
Balooctl 5.69.0
from Neon Testing
KDE Plasma 5.18.4
KDE Frameworks 5.69.0
Qt 5.14.1
ADDITIONAL INFORMATION:
Purging the database without disabling it works as expected; that is
balooctl purge
balooctl status
purges the database and restarts the indexing fine.
Maybe a regression between Frameworks 5.67 and 5.68
--
You are receiving this mail because:
You are watching all bug changes.
