Summary: | Baloo index service crash | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | jordan.freeman |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | ascaris, caulier.gilles, kde-bugs, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.45.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
jordan.freeman
2018-07-08 23:03:52 UTC
*** Bug 396973 has been marked as a duplicate of this bug. *** Created attachment 115355 [details]
New crash information added by DrKonqi
baloo_file (5.50.0) using Qt 5.11.1
- What I was doing when the application crashed:
Simply attempted to start the file indexer. It's not enabled, so I enable it using the file indexer monitor program., It begins nitial indexing, and crashes less than a minute later, every time.
Each time, It reports a segfault in the little ladybug icon that appears in the systray, though this time the backtrace says it was a bus error. Trying to report this error sometimes causes DrKonqi to segfault too before the report is complete.
As far as I know, there are no hardware issues with the PC. It previously ran Mint 19 Cinnamon flawlessly before I switched to KDE.
-- Backtrace (Reduced):
#6 __memmove_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:371
#7 0x00007f214a57f923 in memcpy (__len=1070078608, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8 Baloo::PostingCodec::decode (this=this@entry=0x7f213fc81a47, arr=...) at ./src/codecs/postingcodec.cpp:42
#9 0x00007f214a5713e4 in Baloo::PostingDB::get (this=this@entry=0x7f213fc81b30, term=...) at ./src/engine/postingdb.cpp:100
#10 0x00007f214a57d260 in Baloo::WriteTransaction::commit (this=0x7ee13004d220) at ./src/engine/writetransaction.cpp:259
*** This bug has been marked as a duplicate of bug 394404 *** *** This bug has been marked as a duplicate of bug 357206 *** *** This bug has been marked as a duplicate of bug 367480 *** |