https://bugs.kde.org/show_bug.cgi?id=371955

Marc Streckfuß <marc.streckf...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marc.streckf...@gmail.com

--- Comment #2 from Marc Streckfuß <marc.streckf...@gmail.com> ---
#372606 and #374758 are duplicates of this bug.

Using GDB and the Debug-Symbols I found out that the actual root of this is a
corrupted MDB Database probably from Baloo.
There are some forum posts that one should rename ~/.local/share/baloo which
might trigger a rebuild.

Also see #360946 talking about the fact that "Launching Konsole from KRunner"
corrupts the database. This Corruption should not actually happen either.


The Output from Krunner itself is: 
true
true
true
session switching to "Disc"
mdb.c:5697: Assertion 'IS_LEAF(mp)' failed in mdb_cursor_next()

The Backtrace:
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
__GI_abort () at abort.c:89
?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
mdb_cursor_get () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
Baloo::PostingDB::prefixIter(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
Baloo::Query::exec() () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
Plasma::AbstractRunner::performMatch ( this=0x5555564345d0, localContext=...)
at ./src/abstractrunner.cpp:131
ThreadWeaver::Executor::run(QSharedPointer<ThreadWeaver::JobInterface> const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
QThreadPrivate::start (arg=0x555555dacf30) at thread/qthread_unix.cpp:341
start_thread (arg=0x7fffc0025700) at pthread_create.c:333
clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 


So technically there are two bugs here:
1. Baloo not properly handling corrupted data sets (#360946 indicates that you
can just skip that set). We have seen multiple error sources in MDB for that,
so it's not just prefixIter() but rather at an early stage.

2. Baloo/Krunner corrupting that DataSet (#360946 saying that you can reproduce
it by launching Konsole from Krunner).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to