Summary: | Baloo crashes at KDE session start. | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Kai T. Ohlhus <k.ohlhus> |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | nate, wantoyek |
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
Kai T. Ohlhus
2019-01-29 06:21:54 UTC
Created attachment 117782 [details]
New crash information added by DrKonqi
baloo_file (5.54.0) using Qt 5.12.0
Every login always displays this crash
Operating System: openSUSE Tumbleweed 20190126
KDE Plasma Version: 5.14.5
Qt Version: 5.12.0
KDE Frameworks Version: 5.54.0
Kernel Version: 4.20.2-1-default
OS Type: 64-bit
Processors: 3 × AMD Athlon(tm) II X3 440 Processor
Memory: 7,8 GiB of RAM
-- Backtrace (Reduced):
#7 0x00007fbd004868cd in memcpy (__len=1, __src=0x7f7cec1ae520, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34
#8 Baloo::PostingCodec::decode (this=this@entry=0x7fbcf9e5b8c7, arr=...) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/codecs/postingcodec.cpp:42
#9 0x00007fbd00473ee9 in Baloo::PostingDB::get (this=this@entry=0x7fbcf9e5b9b0, term=...) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/postingdb.cpp:100
#10 0x00007fbd0048413a in Baloo::WriteTransaction::commit (this=0x7f7cec003400) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/writetransaction.cpp:275
#11 0x00007fbd0047a712 in Baloo::Transaction::commit (this=this@entry=0x7fbcf9e5bae0) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/engine/transaction.cpp:269
*** This bug has been marked as a duplicate of bug 357206 *** Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 372880, bug 395888, bug 367480 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9 src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0 -1 src/engine/documenturldb.cpp M +4 -3 src/engine/documenturldb.h M +4 -5 src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0 -2 src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4 -4 src/engine/transaction.h M +3 -2 src/file/extractorprocess.cpp M +5 -5 src/file/fileindexscheduler.cpp M +5 -4 src/file/indexcleaner.cpp M +0 -1 src/file/main.cpp M +1 -1 src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d |