[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [frameworks-baloo] [Bug 387672] Baloo File Extraction Error
From:       Logan Rathbone <bugzilla_noreply () kde ! org>
Date:       2018-08-08 22:28:38
Message-ID: bug-387672-17878-NYtIwYk6js () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=387672

Logan Rathbone <poprocks@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |poprocks@gmail.com

--- Comment #27 from Logan Rathbone <poprocks@gmail.com> ---
My experience with Baloo is that it has virtually no sane error handling or
database recovery mechanism. See the bug I ultimately reported yesterday:
https://bugs.kde.org/show_bug.cgi?id=397255

Try deleting and rebuilding the baloo database. Preferably while logged out of
KDE/Xorg, run:

rm -f ~/.local/share/baloo/index*

And then re-launch KDE.

Adding 'only basic indexing=true' to ~/.config/baloofilerc may mitigate further
issues. Once the baloo database gets corrupt once, my experience is it never
recovers and needs to be rebuilt from scratch.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]