https://bugs.kde.org/show_bug.cgi?id=399849
--- Comment #15 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
(In reply to Patrick Silva from comment #13)
> Created attachment 115726 [details]
> 26 backtraces
>
> This attachment contains 26 backtraces.
> Maybe some of them can help you to find the problem.
The backtraces do not contain sufficient data, most importantly the document
id. Without it, it is not possible to tell which database entry is responsible
for the crash(es).
The only other approach is to run something like 'find <dir> -type f -ls -exec
balooshow -x \{\} \;' and see where it crashes.
--
You are receiving this mail because:
You are watching all bug changes.
