https://bugs.kde.org/show_bug.cgi?id=497648
Giuseppe Della Bianca <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Giuseppe Della Bianca <[email protected]> --- I had a very similar problem. The main problem is that the akonadi server doesn't report the path to the database with problems. This is how I solved it - Stop akonadi for example: akonadictl stop akonadictl status - Stop baloo for example: ps -ef | grep -i balo xxx 7653 3297 0 08:54 ? 00:00:00 /usr/libexec/baloorunner kill -9 7653 ps -ef | grep -i balo - Removes the akonadi and baloo search databases ~/.local/share/akonadi/search_db/ ~/.local/share/baloo/ - Restart akonadi and baloo (preferably a system reboot) - Force rebuilding the indexing For example, from the akonadi console Find and select the indexing agent Put it offline Put it online WARNING, This procedure should only affect indexing, but there's always a risk of data loss, you should have a backup and know how to restore it. -- You are receiving this mail because: You are watching all bug changes.
