https://bugs.kde.org/show_bug.cgi?id=362333
--- Comment #1 from Steve Youngs <st...@steveyoungs.com> ---
I seem to have found a way around this.
`balooctl status' was telling me that there wasn't any files indexed which made
me think that this bug was biting pretty early in the process and it wasn't
even getting to the initial indexing stage. I tentatively tried 'balooctl
index somedir/*' and that gave me a few files in the index.
I then decided (probably foolishly) that if I could manually index one
directory, why not do the whole dang lot, so...
$ find ${HOME} -type d -exec sh -c 'balooctl index {}/*' \;
That took a LONG time, I can't tell you exactly how long because I stopped it
after it went beyond 24 hours! And it hit a few bumps along the way. Had a
few of
"ASSERT failure in PositionDB::put: "MDB_MAP_FULL: Environment mapsize limit
reached", file /usr/src/kde/kf5src/frameworks/baloo/src/engine/positiondb.cpp,
line 80 "
At this point I had just on 170K files in the index (indexer wasn't running).
I crossed my fingers and restarted KDE. The bug hit just like always. Then it
occurred to me that the bug was preventing the initial indexing, but I had
pretty much done that manually now. ~/.config/baloofilerc hinted that the
initial indexing had not been done. So maybe all I had to do was change the
config...
$ sed -i 's/\(first run=\)true/\1false/' ~/.config/baloofilerc
More finger crossing, another KDE restart. This time... success! Didn't get
the crash, and baloo seems to be functioning properly. Searching via krunner,
or baloosearch is working just how I'd expect. balooshow is returning good
info. New files are getting added to the index automatically, likewise deleted
files are being removed.
$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 170229 / 170229 files
Current size of index is 1,021.54 MiB
I am now happy and this bug is no longer affecting me.
--
You are receiving this mail because:
You are watching all bug changes.
