https://bugs.kde.org/show_bug.cgi?id=475695
Bug ID: 475695
Summary: baloo_file_extractor crash on login
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 5.110.0
Platform: Compiled Sources
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #1 from Zack Weinberg ---
I can't figure out how to restart baloo_file_extractor by hand after this
crash.
"balooctl enable" says the indexer is already running, which is not true per
ps. If I run baloo_file_extractor in a
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #2 from Zack Weinberg ---
This doesn't look right to me:
$ ls -lh ~/.local/share/baloo
total 2.3G
-rw-r--r-- 1 zack zack 2.3G Oct 13 11:43 index
-rw-r--r-- 1 zack zack 8.0K Oct 16 09:43 index-lock
$ mdb_stat -n ~/.local/share/baloo/
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #3 from Zack Weinberg ---
It turns out I was using mdb_stat wrong, and the index _isn't_ a giant
mostly-empty shell. However, mdb_copy -c also crashes inside memcpy when
applied to the index file, and mdb_dump -apn prints
/us
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #4 from Zack Weinberg ---
A reindex from scratch ran to completion with no issues.
$ balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 143,490
Files waiting for content indexing: 0
Files failed to index
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #6 from Zack Weinberg ---
$ python3 dl/baloo-checkdb.py .local/share/baloo.bad/index
Loading DB from .local/share/baloo.bad/index...
Traceback (most recent call last):
File "/home/zack/dl/baloo-checkdb.py", line 265, in
https://bugs.kde.org/show_bug.cgi?id=475695
--- Comment #17 from Zack Weinberg ---
In that case I should think this can be closed. (I'm no longer using KDE so I
can't test it myself, regrettably.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475695
Zack Weinberg changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED