can confirm same behavior on openSUSE tumblweed, plasma 5.12, KF5 5.42, QT 5.10.

Also happens on Arch Linux

*** Bug 362222 has been marked as a duplicate of this bug. ***

*** Bug 368733 has been marked as a duplicate of this bug. ***

*** Bug 369184 has been marked as a duplicate of this bug. ***

*** Bug 370727 has been marked as a duplicate of this bug. ***

*** Bug 370903 has been marked as a duplicate of this bug. ***

*** Bug 371382 has been marked as a duplicate of this bug. ***

*** Bug 371784 has been marked as a duplicate of this bug. ***

*** Bug 383101 has been marked as a duplicate of this bug. ***

See also bug 389625. Michael possibly looks into this.

*** Bug 390127 has been marked as a duplicate of this bug. ***

*** Bug 392094 has been marked as a duplicate of this bug. ***

*** Bug 364356 has been marked as a duplicate of this bug. ***

*** Bug 394918 has been marked as a duplicate of this bug. ***

*** Bug 394916 has been marked as a duplicate of this bug. ***

*** Bug 393945 has been marked as a duplicate of this bug. ***

*** Bug 394662 has been marked as a duplicate of this bug. ***

*** Bug 394404 has been marked as a duplicate of this bug. ***

*** Bug 393583 has been marked as a duplicate of this bug. ***

*** Bug 373626 has been marked as a duplicate of this bug. ***

*** Bug 393896 has been marked as a duplicate of this bug. ***

*** Bug 393756 has been marked as a duplicate of this bug. ***

*** Bug 393494 has been marked as a duplicate of this bug. ***

*** Bug 385187 has been marked as a duplicate of this bug. ***

*** Bug 389455 has been marked as a duplicate of this bug. ***

*** Bug 390824 has been marked as a duplicate of this bug. ***

*** Bug 392920 has been marked as a duplicate of this bug. ***

*** Bug 394637 has been marked as a duplicate of this bug. ***

*** Bug 396402 has been marked as a duplicate of this bug. ***

*** Bug 394916 has been marked as a duplicate of this bug. ***

*** Bug 396277 has been marked as a duplicate of this bug. ***

(My DrKonqi crash report: Bug 396277)
In my case, this behaviour appeared after the following upgrade:
Qt Version: 5.6.2 upgraded to 5.9.4;
Frameworks Version: 5.32.0 upgraded to 5.45.0;
(Distribution upgrade from openSUSE Leap 42.3 to Leap 15.0).
------------------------------------------------------------
I noticed that, with the updated system version and, a "fresh" test user, Baloo didn't crash.
Also not after I enabled the PIM plugin in the Digital Clock -- akonadi started.
Also not with a user which doesn't use the Kontact PIM -- only digiKam and Oracle's VirtualBox -- akonadi is not started for this user.
------------------------------------------------------------
For the case of the user which was suffering the Baloo crashes I did the following from a VT with the Display Manager stopped:
 1. Removed the following files in '~/.config/':
    baloorc
    baloofilerc
    baloofileinformationrc
 2. Removed the entire contents of '~/.local/share/baloo/':
    index
    index-lock
    KDE PIM Kontact directories
 3. Restarted the Display Manager and logged in the user with the "Baloo
    crashing issue".
------------------------------------------------------------
Baloo doesn't crash any more.
------------------------------------------------------------
My guess at the root cause:
 * Outdated Baloo configuration files and an outdated index database cause
   an exception with the current Baloo implementation.

I expect Baloo will take care of not any more usable configuration files and definitely that it will update the database (structure, anything) so the index file will not be needed to be deleted and that all the files will not be indexed from scratch.

Created attachment 114108 [details]
New crash information added by DrKonqi

baloo_file (5.45.0) using Qt 5.9.4

- What I was doing when the application crashed:

Nothing special -- I had logged in and was writing an e-Mail with KMail which had some (large) photos as attachments when I noticed that, Baloo had crashed.
Baloo File Indexing Daemon (baloo_file), signal: Aborted -- mdb_assert_fail -- mdb_page_dirty …

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x00007efdef92a6c1 in __GI_abort () at abort.c:79
#8  0x00007efded6c2922 in mdb_assert_fail (env=0x55beddd98390, expr_txt=expr_txt@entry=0x7efded6c43af "rc == 0", func=func@entry=0x7efded6c4ce8 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7efded6c4390 "mdb.c") at mdb.c:1487
#9  0x00007efded6b7e05 in mdb_page_dirty (txn=0x55beddd99750, mp=<optimized out>) at mdb.c:2071
#10 0x00007efded6b8fea in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffe994e8538, mc=<optimized out>) at mdb.c:2252

Forgot to mention:
 * The contents of ~/.local/share/baloo/ have been removed several times.
 * All files related to Baloo in ~/.config/ (for example: baloofilerc) have been
   removed several times.
Today's report is a double Baloo crash
 -- two times DrKonqui in quick succession …

(In reply to Don Curtis from comment #33)
> (My DrKonqi crash report: Bug 396277)
> In my case, this behaviour appeared after the following upgrade:
> Qt Version: 5.6.2 upgraded to 5.9.4;
> Frameworks Version: 5.32.0 upgraded to 5.45.0;
> (Distribution upgrade from openSUSE Leap 42.3 to Leap 15.0).
> ------------------------------------------------------------
> I noticed that, with the updated system version and, a "fresh" test user,
> Baloo didn't crash.
> Also not after I enabled the PIM plugin in the Digital Clock -- akonadi
> started.
> Also not with a user which doesn't use the Kontact PIM -- only digiKam and
> Oracle's VirtualBox -- akonadi is not started for this user.
> ------------------------------------------------------------
> For the case of the user which was suffering the Baloo crashes I did the
> following from a VT with the Display Manager stopped:
>  1. Removed the following files in '~/.config/':
>     baloorc
>     baloofilerc
>     baloofileinformationrc
>  2. Removed the entire contents of '~/.local/share/baloo/':
>     index
>     index-lock
>     KDE PIM Kontact directories
>  3. Restarted the Display Manager and logged in the user with the "Baloo
>     crashing issue".
> ------------------------------------------------------------
> Baloo doesn't crash any more.
> ------------------------------------------------------------
> My guess at the root cause:
>  * Outdated Baloo configuration files and an outdated index database cause
>    an exception with the current Baloo implementation.

Tried this (Fedora 27 - has been a recurring issue since Fedora 22).
So far, no more crashes.
I guess the suggestion above WRT outdated files may be on the money.

*** Bug 397582 has been marked as a duplicate of this bug. ***

This has been tracked in the OpenLDAP (lmdb) Issue Tracker System, ITS 8756.

The fix has been cherry-picked into the liblmdb-0_9_22 package for openSUSE Tumbleweed and is part of the latest snapshot (20181012).

What's the full URL of the upstream bug report?

(In reply to Nate Graham from comment #40)
> What's the full URL of the upstream bug report?

https://www.openldap.org/its/index.cgi/Software%20Bugs?id=8756;selectid=8756

*** Bug 400498 has been marked as a duplicate of this bug. ***

*** Bug 396078 has been marked as a duplicate of this bug. ***

*** Bug 387672 has been marked as a duplicate of this bug. ***

*** Bug 389625 has been marked as a duplicate of this bug. ***

*** Bug 388897 has been marked as a duplicate of this bug. ***

*** Bug 396658 has been marked as a duplicate of this bug. ***

*** Bug 401288 has been marked as a duplicate of this bug. ***

*** Bug 400728 has been marked as a duplicate of this bug. ***

*** Bug 399851 has been marked as a duplicate of this bug. ***

*** Bug 390200 has been marked as a duplicate of this bug. ***

*** Bug 380080 has been marked as a duplicate of this bug. ***

*** Bug 358729 has been marked as a duplicate of this bug. ***

*** Bug 353483 has been marked as a duplicate of this bug. ***

*** Bug 387104 has been marked as a duplicate of this bug. ***

*** Bug 395475 has been marked as a duplicate of this bug. ***

*** Bug 373179 has been marked as a duplicate of this bug. ***

*** Bug 376781 has been marked as a duplicate of this bug. ***

*** Bug 378340 has been marked as a duplicate of this bug. ***

*** Bug 378750 has been marked as a duplicate of this bug. ***

*** Bug 386987 has been marked as a duplicate of this bug. ***

*** Bug 385187 has been marked as a duplicate of this bug. ***

*** Bug 402510 has been marked as a duplicate of this bug. ***

*** Bug 402492 has been marked as a duplicate of this bug. ***

*** Bug 403013 has been marked as a duplicate of this bug. ***

*** Bug 403107 has been marked as a duplicate of this bug. ***

*** Bug 403010 has been marked as a duplicate of this bug. ***

*** Bug 403343 has been marked as a duplicate of this bug. ***

I have lmdb 0.9.23 installed on Arch Linux and baloo is still crashing immediately after login.

With the same backtrace as this bug? Baloo crashes in a lot of different ways. :/

(In reply to Nate Graham from comment #70)
> With the same backtrace as this bug? Baloo crashes in a lot of different
> ways. :/

Mine does crash too, but it seems to be a different backtrace. Should I create a new bug report or post here?

(In reply to Nate Graham from comment #70)
> With the same backtrace as this bug?
Different.
drkonqi says that the backtrace is duplicate of bug 367480.

Makes sense, since that one is still open.

If DrKonqi reports that your Baloo crash is a duplicate, there's no need to file it. We know about these issues... we just need to get them fixed... somehow...

*** Bug 403741 has been marked as a duplicate of this bug. ***

*** Bug 404239 has been marked as a duplicate of this bug. ***

*** Bug 404688 has been marked as a duplicate of this bug. ***

*** Bug 404940 has been marked as a duplicate of this bug. ***

*** Bug 405072 has been marked as a duplicate of this bug. ***

*** Bug 405480 has been marked as a duplicate of this bug. ***

*** Bug 406173 has been marked as a duplicate of this bug. ***

*** Bug 380111 has been marked as a duplicate of this bug. ***

*** Bug 406704 has been marked as a duplicate of this bug. ***

*** Bug 407342 has been marked as a duplicate of this bug. ***

*** Bug 408008 has been marked as a duplicate of this bug. ***

*** Bug 408018 has been marked as a duplicate of this bug. ***

Created attachment 120531 [details]
baloo_file_extractor log crash

I've finished one project and deleted the detritus. Log out / Log in. Crash.

*** Bug 408293 has been marked as a duplicate of this bug. ***

*** Bug 410134 has been marked as a duplicate of this bug. ***

*** Bug 409829 has been marked as a duplicate of this bug. ***

*** Bug 410494 has been marked as a duplicate of this bug. ***

We continue to amass duplicates even from users of rolling release distros with recent Frameworks versions and LMDB 0.9.23 or later. Re-opening. :(

Baloo never used to work on my machine and it was impossible to search for files in dolphin.

Executing 'balooctl enable' printed the message 'KCrash: Application 'baloo_file' crashing...'

Today I found the hint to remove the baloo index file:

balooctl purge
balooctl enable

After a few seconds, the index was created and now file search in dolphin works (by name only, not by content, enabling content indexer lead to another KCrash).

i get no more crash since update(what one ?)

openSuse Argon 15.1
kde app 19.04.3
plasma 5.16.3
kde framework 5.60.0
qt 5.13.0

(In reply to Philippe ROUBACH from comment #93)
> i get no more crash since update(what one ?)
> 
> openSuse Argon 15.1
> kde app 19.04.3
> plasma 5.16.3
> kde framework 5.60.0
> qt 5.13.0

Well, with 15.1 and frameworks 5.55 (stock as all the rest of the system) you get first no crash after erasing the indexes and rebuilding them. But then the problem reappears in all its ugliness. So for Opensuse 15.1 (as long as you do not use some extra repos) you do have it to a full extend.

For those which does not know what openSuse Argon is, Argon is a Neon with opensuse basement. Then we get permanently last kde updates as with Neon

And yes crash did not appear again after recreating baloo index by deleting all about baloo in ~/.config folder and ~/.local/share/

what helped in my case was deleting index file @ ~/.local/share/baloo/ and re indexing the hard drive. it took baloo 2-3 hours to accomplish this task.

(In reply to plasmapeleng from comment #96)
> what helped in my case was deleting index file @ ~/.local/share/baloo/ and
> re indexing the hard drive. it took baloo 2-3 hours to accomplish this task.

yes, this worked in my case but only a few weeks. Now I am back to the original misery. Unfortunately the bugfix was not backported to Leap 15.1 (maybe lack of motivation or personnel) and so the workaround is not long term. Unfortunately.

(In reply to stakanov from comment #97)
> (In reply to plasmapeleng from comment #96)
> > what helped in my case was deleting index file @ ~/.local/share/baloo/ and
> > re indexing the hard drive. it took baloo 2-3 hours to accomplish this task.
> 
> yes, this worked in my case but only a few weeks. Now I am back to the
> original misery. Unfortunately the bugfix was not backported to Leap 15.1
> (maybe lack of motivation or personnel) and so the workaround is not long
> term. Unfortunately.

that's annoying indeed. have no idea what the deal is though. was a bit nervous after the initial install. failed to index the drive properly by the first runs. we'll see, have no problems with baloo so far

Created attachment 122125 [details]
New crash information added by DrKonqi

baloo_file (5.55.0) using Qt 5.9.7

- What I was doing when the application crashed:
Anything thats related with search and indexing, when system starts indexing it just crashing when you loged in to your account. That's happening since brand new install Leap 15. Still same problem untill today with 15.1 Have to use other search app.

-- Backtrace (Reduced):
#8  0x00007f9c648d28b2 in mdb_assert_fail (env=0x559add3b02a0, expr_txt=expr_txt@entry=0x7f9c648d433f "rc == 0", func=func@entry=0x7f9c648d4c78 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7f9c648d4320 "mdb.c") at mdb.c:1487
#9  0x00007f9c648c7d85 in mdb_page_dirty (txn=0x559add3b1700, mp=<optimized out>) at mdb.c:2071
#10 0x00007f9c648c8f6a in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f9c5dd5b038, mc=<optimized out>) at mdb.c:2252
#11 0x00007f9c648c91d9 in mdb_page_touch (mc=mc@entry=0x7f9c5dd5b570) at mdb.c:2370
#12 0x00007f9c648cacaf in mdb_cursor_touch (mc=mc@entry=0x7f9c5dd5b570) at mdb.c:6273

(In reply to plasmapeleng from comment #98)
> (In reply to stakanov from comment #97)
> > (In reply to plasmapeleng from comment #96)
> > > what helped in my case was deleting index file @ ~/.local/share/baloo/ and
> > > re indexing the hard drive. it took baloo 2-3 hours to accomplish this task.
> > 
> > yes, this worked in my case but only a few weeks. Now I am back to the
> > original misery. Unfortunately the bugfix was not backported to Leap 15.1
> > (maybe lack of motivation or personnel) and so the workaround is not long
> > term. Unfortunately.
> 
> that's annoying indeed. have no idea what the deal is though. was a bit
> nervous after the initial install. failed to index the drive properly by the
> first runs. we'll see, have no problems with baloo so far

yes, you are right, i confirm. baloo has crashed. to bring it to senses i've disabled "index file content" in the factory state. now index file @ ~/.local/share/baloo/ is some 45 Mb instead of 1.3 Gb and the initial indexing was almost instant.

*** Bug 410916 has been marked as a duplicate of this bug. ***

*** Bug 411139 has been marked as a duplicate of this bug. ***

*** Bug 411064 has been marked as a duplicate of this bug. ***

*** Bug 411192 has been marked as a duplicate of this bug. ***

Created attachment 122303 [details]
attachment-23301-0.html

See and try out options suggested here (worked to solve my baloo_file crash
problem) : https://bbs.archlinux.org/viewtopic.php?id=193169

On Thu, Aug 22, 2019 at 6:17 PM Stefan Brüns <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=389848
>
> Stefan Brüns <stefan.bruens@rwth-aachen.de> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |pedrogron77@gmail.com
>
> --- Comment #104 from Stefan Brüns <stefan.bruens@rwth-aachen.de> ---
> *** Bug 411192 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

*** Bug 411660 has been marked as a duplicate of this bug. ***

*** Bug 411706 has been marked as a duplicate of this bug. ***

*** Bug 411839 has been marked as a duplicate of this bug. ***

*** Bug 412567 has been marked as a duplicate of this bug. ***

*** Bug 412359 has been marked as a duplicate of this bug. ***

*** Bug 412780 has been marked as a duplicate of this bug. ***

*** Bug 413060 has been marked as a duplicate of this bug. ***

*** Bug 413289 has been marked as a duplicate of this bug. ***

*** Bug 413421 has been marked as a duplicate of this bug. ***

*** Bug 413558 has been marked as a duplicate of this bug. ***

*** Bug 413797 has been marked as a duplicate of this bug. ***

*** Bug 413773 has been marked as a duplicate of this bug. ***

Created attachment 123898 [details]
New crash information added by DrKonqi

baloo_file (5.64.0) using Qt 5.13.2

- What I was doing when the application crashed:

The crash happens at every single login. 

- Unusual behavior I noticed:

Crash

- Custom settings of the application:

No custom settings. Crash happens with the vailla kernel and also with the zen kernel. I use the Breeze theme and no custom settings.

-- Backtrace (Reduced):
#13 0x00007fa7477be619 in mdb_cursor_put () from /usr/lib/liblmdb.so
#14 0x00007fa7477c14ab in mdb_put () from /usr/lib/liblmdb.so
#15 0x00007fa7492d0b7a in Baloo::DocumentTimeDB::put(unsigned long long, Baloo::DocumentTimeDB::TimeInfo const&) () from /usr/lib/libKF5BalooEngine.so.5
#16 0x00007fa7492f7a95 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib/libKF5BalooEngine.so.5
#17 0x00007fa7492ea695 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib/libKF5BalooEngine.so.5

*** Bug 405101 has been marked as a duplicate of this bug. ***

*** Bug 414240 has been marked as a duplicate of this bug. ***

*** Bug 414397 has been marked as a duplicate of this bug. ***

Created attachment 124273 [details]
New crash information added by DrKonqi

baloo_file (5.64.0) using Qt 5.13.1

Just logged into KDE and was greetet with the Crash Dialog of Ballo, happens since a long time now, I just decited to fianly send an error report because it is still not fixed after month.

-- Backtrace (Reduced):
#8  0x00007fc3c31416f3 in mdb_assert_fail (env=0x56209e87cc70, expr_txt=expr_txt@entry=0x7fc3c314302f "rc == 0", func=func@entry=0x7fc3c3143978 <__func__.7210> "mdb_page_dirty", line=line@entry=2127, file=0x7fc3c3143010 "mdb.c") at mdb.c:1542
#9  0x00007fc3c3136435 in mdb_page_dirty (mp=<optimized out>, txn=0x56209e87e070) at mdb.c:2114
#10 mdb_page_dirty (txn=0x56209e87e070, mp=<optimized out>) at mdb.c:2114
#11 0x00007fc3c3137676 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7fc3bfa1de78, mc=<optimized out>) at mdb.c:2308
#12 0x00007fc3c31378b3 in mdb_page_touch (mc=mc@entry=0x7fc3bfa1e3b0) at mdb.c:2495

Same Problem.

Application: baloo_file_extractor (5.64.0)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 4.20.17-042017-generic x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
Error message after login.

The crash can be reproduced every time.

-- Backtrace:
Application: Extraktor súborov Baloo (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa242f5fc80 (LWP 2379))]

Thread 3 (Thread 0x7fa22f5d1700 (LWP 2398)):
#0  0x00007fa23fa25bf9 in __GI___poll (fds=0x7fa22801a8e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fa23c0ea5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa23c0ea6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa240378b9b in QEventDispatcherGlib::processEvents (this=0x7fa228000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fa24031906a in QEventLoop::exec (this=this@entry=0x7fa22f5d0d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x00007fa2401343aa in QThread::exec (this=this@entry=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531
#6  0x00007fa241d2f0e5 in QDBusConnectionManager::run (this=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#7  0x00007fa240135b52 in QThreadPrivate::start (arg=0x7fa241fa6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:360
#8  0x00007fa23e28d6db in start_thread (arg=0x7fa22f5d1700) at pthread_create.c:463
#9  0x00007fa23fa3288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fa234968700 (LWP 2391)):
#0  0x00007fa23fa25bf9 in __GI___poll (fds=0x7fa234967ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fa23bc79747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fa23bc7b36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fa23774de10 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007fa240135b52 in QThreadPrivate::start (arg=0x559965564f60) at thread/qthread_unix.cpp:360
#5  0x00007fa23e28d6db in start_thread (arg=0x7fa234968700) at pthread_create.c:463
#6  0x00007fa23fa3288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fa242f5fc80 (LWP 2379)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x00007fa23f951801 in __GI_abort () at abort.c:79
#8  0x00007fa23ec3d932 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x00007fa23ec327b5 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x00007fa23ec339bb in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x00007fa23ec33c29 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x00007fa23ec35854 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#13 0x00007fa23ec389ee in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#14 0x00007fa23ec3b72b in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#15 0x00007fa2423db60c in Baloo::PositionDB::put (this=this@entry=0x7fff97965340, term=..., list=...) at ./src/engine/positiondb.cpp:82
#16 0x00007fa2423ed16e in Baloo::WriteTransaction::commit (this=0x5599655bf4e0) at ./src/engine/writetransaction.cpp:333
#17 0x00007fa2423e3dd1 in Baloo::Transaction::commit (this=0x5599655c5eb0) at ./src/engine/transaction.cpp:304
#18 0x00005599650132f4 in Baloo::App::processNextFile (this=0x7fff97965b10) at ./src/file/extractor/app.cpp:119
#19 0x00007fa2403586b4 in QtPrivate::QSlotObjectBase::call (a=0x7fff979654c0, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#20 QSingleShotTimer::timerEvent (this=0x5599655da200) at kernel/qtimer.cpp:318
#21 0x00007fa24034c3eb in QObject::event (this=0x5599655da200, e=<optimized out>) at kernel/qobject.cpp:1282
#22 0x00007fa24111feac in QApplicationPrivate::notify_helper (this=this@entry=0x55996553d120, receiver=receiver@entry=0x5599655da200, e=e@entry=0x7fff97965800) at kernel/qapplication.cpp:3703
#23 0x00007fa2411274b0 in QApplication::notify (this=0x7fff97965ae0, receiver=0x5599655da200, e=0x7fff97965800) at kernel/qapplication.cpp:3449
#24 0x00007fa24031af08 in QCoreApplication::notifyInternal2 (receiver=0x5599655da200, event=0x7fff97965800) at kernel/qcoreapplication.cpp:1095
#25 0x00007fa240378009 in QTimerInfoList::activateTimers (this=0x55996559c930) at kernel/qtimerinfo_unix.cpp:643
#26 0x00007fa2403787d1 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#27 0x00007fa23c0ea417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fa23c0ea650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fa23c0ea6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007fa240378b7f in QEventDispatcherGlib::processEvents (this=0x559965549a20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#31 0x00007fa24031906a in QEventLoop::exec (this=this@entry=0x7fff97965a50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#32 0x00007fa2403223e0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1403
#33 0x0000559965011c5d in main (argc=<optimized out>, argv=<optimized out>) at ./src/file/extractor/main.cpp:59

*** Bug 415416 has been marked as a duplicate of this bug. ***

*** Bug 412847 has been marked as a duplicate of this bug. ***

HI,
Due to several kubuntu distro updates since my origonal bug
report and the lack of errors recieved concerning Balloo.
Although I would not say the origonal bug is fixed, it does
not seem evident in a new Minimal install of Kubuntu 19.10.
Whether this is  due to updates or different baloo packages
used  in K19.10 I cannot say.

Unfortunately during upgrades I have lost my origonal bug
report and details,
However, I hope you can at least say the bug does not seem
to affect Kubuntu 19.10 Minimal,

I would also appreciate my removal from the cc list for
this bug,

Thanks

On Mon, 23 Dec 2019 14:07:18 +0000
"Ismael Asensio" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=389848
> 
> Ismael Asensio <isma.af@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|
> |jcbissauge@gmail.com
> 
> --- Comment #125 from Ismael Asensio <isma.af@gmail.com>
> --- *** Bug 412847 has been marked as a duplicate of this
> bug. ***
>

Problem has not occurred again since 2019-08-14 (see comment #93 and #95) and 
openSuse Argon 15.1
kde app 19.04.3
plasma 5.16.3
kde framework 5.60.0
qt 5.13.0

till now 2019-12-23 and
openSuse Argon 15.1
kde app 19.12.0
plasma 5.17.5
kde framework 5.65.0
qt 5.13.1

I've got the crash recently but a "balooctl purge" command to rebuild the index fixed it for me. Seems like Baloo doesn't like it when there's some data corrupted or so.

Created attachment 125138 [details]
New crash information added by DrKonqi

baloo_file_extractor (5.62.0) using Qt 5.12.4

- What I was doing when the application crashed: Booting the system

- Unusual behavior I noticed: 1) Wallpaper change; 2) Multiple Error notifications

- Custom settings of the application: Don't know. It's the first time I have been noticed about Baloo. Don't don't what it does

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fabd7fde899 in __GI_abort () at abort.c:79
[...]
#13 0x00007fabd7d0c4db in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#14 0x00007fabd7d0f2db in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#15 0x00007fabd97283e5 in Baloo::DocumentDB::put(unsigned long long, QVector<QByteArray> const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5

*** Bug 417348 has been marked as a duplicate of this bug. ***

*** Bug 417398 has been marked as a duplicate of this bug. ***

*** Bug 417717 has been marked as a duplicate of this bug. ***

Created attachment 126267 [details]
New crash information added by DrKonqi

baloo_file_extractor (5.64.0) using Qt 5.13.2

- What I was doing when the application crashed:

Logged into Plasma X11 and immediately got a baloo_file crash. Logged out, logged into Plasma Wayland and got the same crash. This isn't the first time -- baloo_file starts crashing each month or so until I wipe its database at ~/.local/share/baloo/index .

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f2196284536 in __GI_abort () at abort.c:79
#8  0x00007f2195fb073a in mdb_assert_fail (env=0x560ec71cd000, expr_txt=expr_txt@entry=0x7f2195fb2250 "IS_BRANCH(mc->mc_pg[mc->mc_top])", func=func@entry=0x7f2195fb28f0 <__func__.8090> "mdb_cursor_sibling", line=line@entry=5837, file=0x7f2195fb2010 "mdb.c") at mdb.c:1542
#9  0x00007f2195fa57bf in mdb_cursor_sibling (mc=mc@entry=0x7ffea12f0970, move_right=move_right@entry=1) at mdb.c:5403
#10 0x00007f2195facc62 in mdb_cursor_del0 (mc=0x7ffea12f0970) at mdb.c:8480

*** Bug 417970 has been marked as a duplicate of this bug. ***

*** Bug 417976 has been marked as a duplicate of this bug. ***

Application: baloo_file_extractor (5.67.0)

Qt Version: 5.13.2
Frameworks Version: 5.67.0
Operating System: Linux 4.19.52-gentoo-FC.01 x86_64
Distribution: "Gentoo Base System release 2.6"


I'm hit by this same bug. Rather than add my backtrace, here's what I get in the console when I issue 'balooctl enable':

mdb.c:2127: Assertion 'rc == 0' failed in mdb_page_dirty()
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/var/run/user/1000/kdeinit5__0
KCrash: Application 'baloo_file' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/var/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...

*** Bug 419917 has been marked as a duplicate of this bug. ***

*** Bug 418926 has been marked as a duplicate of this bug. ***

What does the NOR in "Importance: NOR crash" mean?

*** Bug 420677 has been marked as a duplicate of this bug. ***

*** Bug 420615 has been marked as a duplicate of this bug. ***

*** Bug 420296 has been marked as a duplicate of this bug. ***

*** Bug 421728 has been marked as a duplicate of this bug. ***

*** Bug 422483 has been marked as a duplicate of this bug. ***

*** Bug 425484 has been marked as a duplicate of this bug. ***

I'm seeing at least three of these every day. :( Anything I can do to debug, Stefan?

(In reply to Nate Graham from comment #146)
> I'm seeing at least three of these every day. :( Anything I can do to debug,
> Stefan?

And I haven't seen any of these crashes on any of my systems - IIRC, ever. I am indexing most of my disk, though I have excluded sources, so my index is definitely not small either.

There is no clear pattern. Purging the DB seems to help (which indicates the internal structure got broken), but then sometimes the problem reappears.

(In reply to Stefan Brüns from comment #147)
> (In reply to Nate Graham from comment #146)
> > I'm seeing at least three of these every day. :( Anything I can do to debug,
> > Stefan?
> 
> And I haven't seen any of these crashes on any of my systems - IIRC, ever. I
> am indexing most of my disk, though I have excluded sources, so my index is
> definitely not small either.
> 
> There is no clear pattern. Purging the DB seems to help (which indicates the
> internal structure got broken), but then sometimes the problem reappears.


Well, to be honest, I never commented nor opened new bug as it seemed to be linked to this one and I saw some threads of people telling there was no point in opening anything new, and it might even be bothersome because devs were aware of the issue.

But to give you an idea of how much of a problem this can be, I went through months on my Linux with some random freezes of the system, most of the time leading to full crash of the OS when it didn't un-freeze after several *minutes*.

This stopped the day I disabled baloo from systemd.
If this may help you, I'm not an exclusive KDE user, have several DE/WM installed and sometimes jump from one to another, and it seems that services like Baloo are started, whether KDE is started or not rather than being part of it, so may it conflict with other similar services such as Gnome's one? Can't tell, I don't know enough of all of this. But imho, this is clearly worth investigating when we talk about minutes OS freezes and most of the time full OS crashes.

Unfortunately, the crashes were so sudden that I never found anything useful from journald nor dmesg.

*** Bug 426195 has been marked as a duplicate of this bug. ***

*** Bug 427742 has been marked as a duplicate of this bug. ***

*** Bug 428123 has been marked as a duplicate of this bug. ***

*** Bug 386702 has been marked as a duplicate of this bug. ***

*** Bug 413485 has been marked as a duplicate of this bug. ***

*** Bug 419346 has been marked as a duplicate of this bug. ***

*** Bug 427480 has been marked as a duplicate of this bug. ***

(In reply to Nate Graham from comment #155)
> *** Bug 427480 has been marked as a duplicate of this bug. ***

good work with dealing with all the duplicates. this  started in 2018 - anyone know why its not being dealt with?  The number of duplicates suggest its a bit of a widespread issue.

(In reply to BingMyBong from comment #156)
> good work with dealing with all the duplicates. this  started in 2018 -
> anyone know why its not being dealt with?  The number of duplicates suggest
> its a bit of a widespread issue.

When I added my first crash dump in 2018, the system was as follows:
 ** Qt Version: 5.6.2 upgraded to 5.9.4;
 ** Frameworks Version: 5.32.0 upgraded to 5.45.0;
 ** (Distribution upgrade from openSUSE Leap 42.3 to Leap 15.0).

Currently, with:
 ** Qt version: 5.12.7
 ** Frameworks version: 5.71.0
 ** Plasma version: 5.18.5
 ** Baloo version: 5.71.0
 ** openSUSE Leap 15.2

Baloo is running smoothly with the following status:

 > LANG=C balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 76,318
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 41.48 MiB
 >

The problem is that it's mostly an upstream issue in LMDB itself, which is not a KDE product. Stefan tried to fix it with an upstream patch, but apparently it did not work. :(

I don't know if there's any way we can work around it in Baloo, but I'm hardly a technical expert in database code.

I have a filed a new upstream bug report and will follow up there: https://bugs.openldap.org/show_bug.cgi?id=9378

The LMDB developers have responded and are asking for an affected database file.

For anybody who can reproduce this issue, I have three questions:
1. Is it reliable? If you restart Baloo, does it immediately crash again?
2. Is your database file below, say, 100 Mb? `balooctl status` will tell you.
3. Are you willing to upload your database to a public location so the LMDB developers can debug it? It's located at ~/.local/share/baloo/index

(In reply to Nate Graham from comment #160)
> The LMDB developers have responded and are asking for an affected database
> file.
> 
> For anybody who can reproduce this issue, I have three questions:
> 1. Is it reliable? If you restart Baloo, does it immediately crash again?
> 2. Is your database file below, say, 100 Mb? `balooctl status` will tell you.
> 3. Are you willing to upload your database to a public location so the LMDB
> developers can debug it? It's located at ~/.local/share/baloo/index

For me, the crashes were kinda random, but (I'm not sure anymore), could happen during high usage computer, causing micro-freezes, or intensive writes (might be related, due to swap), especially, I sometimes suspected it would kind of dislike files that were only partially written and there constantly "reevaluated". Only bare feeling as I have no knowledge on how does it work here. If this might be related, the disk is a SSD and is fully encrypted through LUKS, which might cause read and write to be much more CPU-intensive.

The file currently weight 2.4G. I disabled baloo quite a long time ago now, as you can see:
.rw-r--r--  2.4G clement 22 Feb  0:33  /home/clement/.local/share/baloo/index

It would be hard to upload because, well, I would need to control content for privacy reasons to sanitize data, but it both seems it's a huge amount, and that I have no knowledge of data structure. But I can provide more information if I'm told how to do so.

Looking at what you said above, the size is a lot bigger than it should be, so, maybe if the bug was considered to fixed and it was a database corruption the solution would be to wipe that file out?

On my side, I have luks encrypted home partition, too. The index file is 1Go heavy and is on a professional computer, thus I can't deliver it.

Hi All!

I am on this thread because I reported the same bug. Since then, there
have been a lot of duplicates.

On my side, I am running OpenSUSE Tumbleweed on my media server. It's
a rolling release, and there are frequent updates, pretty much daily,
most of the time.

Many of these updates require a reboot.

I was only ever getting this problem after I had run a distribution
update -"zypper dup", and then rebooted.

For a while, I was frequently getting the same error, but not every
time. I don't recall seeing it for the past few weeks. I will report
it if I see it again.

Tumbleweed is pretty bleeding-edge as far as the kernel and system
libraries are concerned, I think SUSE uses us a beta-testers for their
commercial platforms.

But, this being the case, there is a possibility that the bug has
already been fixed, and just needs to roll out to the majority of
distros.

Kind regards,
Steven.

On Wed, 28 Oct 2020 at 16:21, Papoteur <bugzilla_noreply@kde.org> wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=389848
>
> --- Comment #162 from Papoteur <yves.brungard_mageia@gadz.org> ---
> On my side, I have luks encrypted home partition, too. The index file is 1Go
> heavy and is on a professional computer, thus I can't deliver it.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Hi,
my database is indeed only 28 MB, and I would be OK to give it.

It would be worth to check together that I correctly test to reproduce the crash : Is this cmd & output below relevant ?

> baloo_file
mdb.c:2127: Assertion 'rc == 0' failed in mdb_page_dirty()
KCrash: Attempting to start /usr/bin/baloo_file
KCrash: Application 'baloo_file' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
Failed to register via dbus. Another instance is running

Regards

Good day, all!

Sad to report that after a "zypper dup" and reboot yesterday, still
got the same error.

I couldn't report the stacktrace via the OS reporting mechanism, the
message said that there was no email address associated with the
component.

Kind regards,
Steven.

On Wed, 28 Oct 2020 at 16:36, Steven Swart <steven.swart@gmail.com> wrote:
>
> Hi All!
>
> I am on this thread because I reported the same bug. Since then, there
> have been a lot of duplicates.
>
> On my side, I am running OpenSUSE Tumbleweed on my media server. It's
> a rolling release, and there are frequent updates, pretty much daily,
> most of the time.
>
> Many of these updates require a reboot.
>
> I was only ever getting this problem after I had run a distribution
> update -"zypper dup", and then rebooted.
>
> For a while, I was frequently getting the same error, but not every
> time. I don't recall seeing it for the past few weeks. I will report
> it if I see it again.
>
> Tumbleweed is pretty bleeding-edge as far as the kernel and system
> libraries are concerned, I think SUSE uses us a beta-testers for their
> commercial platforms.
>
> But, this being the case, there is a possibility that the bug has
> already been fixed, and just needs to roll out to the majority of
> distros.
>
> Kind regards,
> Steven.
>
> On Wed, 28 Oct 2020 at 16:21, Papoteur <bugzilla_noreply@kde.org> wrote:
> >
> > https://bugs.kde.org/show_bug.cgi?id=389848
> >
> > --- Comment #162 from Papoteur <yves.brungard_mageia@gadz.org> ---
> > On my side, I have luks encrypted home partition, too. The index file is 1Go
> > heavy and is on a professional computer, thus I can't deliver it.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

*** Bug 428810 has been marked as a duplicate of this bug. ***

*** Bug 430113 has been marked as a duplicate of this bug. ***

*** Bug 430455 has been marked as a duplicate of this bug. ***

*** Bug 430731 has been marked as a duplicate of this bug. ***

Solved
Used Procedure:   
- Open "Configuracion del Sistema" > Espacio de trabajo > "Buscar" > "Busqueda de archivos".
  Unselect "Activar Busqueda de archivos"
  Unselect "indexar también contenido de los archivos".
    Click "Apply" 

- Go to /home/user/.local/share/baloo/
     Delete all

- Restart
No errors

probable error: corrupted baloo bdd

I did as suggested in comment 170, performed a restart, cold boot & a logout/login as this is usually I found the 'report the bug messages'.
No crashes or bug messages since.
Thanks for the help & replies.
Laurie J.

*** Bug 437191 has been marked as a duplicate of this bug. ***

*** Bug 437974 has been marked as a duplicate of this bug. ***

*** Bug 440474 has been marked as a duplicate of this bug. ***

Created attachment 141789 [details]
New crash information added by DrKonqi

baloo_file (5.68.0) using Qt 5.12.8

- What I was doing when the application crashed:
Log In
- Custom settings of the application:
Issue started after I install Wayland, tested it, and after removed it.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f9ea55fa859 in __GI_abort () at abort.c:79
[...]
#14 0x00007f9ea4c78a80 in mdb_txn_commit () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#15 0x00007f9ea6178ca7 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
[...]
#19 0x00007f9ea4cdd609 in start_thread (arg=<optimized out>) at pthread_create.c:477

*** Bug 465529 has been marked as a duplicate of this bug. ***

*** Bug 467485 has been marked as a duplicate of this bug. ***

Copying from https://bugs.openldap.org/show_bug.cgi?id=9378

Thanks to assistance from another user, we've made some progress setting up a KDE test environment to reproduce this issue. Using the replay logging facility in this branch https://git.openldap.org/hyc/openldap/-/tree/mplay09?ref_type=heads we collected a trace from one of the crash instances. The suspicious part is excerpted here:

>mdb_put: 0x5638e7e58130, 2, 8[646f6d696e616e74], 16, 0
>mdb_put: 0x5638e7e58130, 3, 8[646f6d696e616e74], 24, 0
>mdb_put: 0x5638e7e58130, 2, 8[74656c6c74616c65], 8, 0
>mdb_put: 0x5638e7e58130, 3, 8[74656c6c74616c65], 11, 0
>mdb_put: 0x5638e7e58130, 2, 3[747874], 56200, 0
>mdb_env_create: 0x559276b2ddc0
>mdb_env_set_maxdbs: 0x559276b2ddc0, 12
>mdb_env_set_mapsize: 0x559276b2ddc0, 274877906944
>mdb_env_open: 0x559276b2ddc0, /home/vm/.local/share/baloo/index, 16793600, 0664
>mdb_txn_begin: 0x559276b2ddc0, (nil), 0 = 0x559276b2f1c0
>mdb_dbi_open: 0x559276b2f1c0, postingdb, 262144 = 2
>mdb_dbi_open: 0x559276b2f1c0, positiondb, 262144 = 3
>mdb_dbi_open: 0x559276b2f1c0, docterms, 262152 = 4
>mdb_dbi_open: 0x559276b2f1c0, docfilenameterms, 262152 = 5
>mdb_dbi_open: 0x559276b2f1c0, docxatrrterms, 262152 = 6
>mdb_dbi_open: 0x559276b2f1c0, idtree, 262152 = 7
>mdb_dbi_open: 0x559276b2f1c0, idfilename, 262152 = 8
>mdb_dbi_open: 0x559276b2f1c0, documenttimedb, 262152 = 9
>mdb_dbi_open: 0x559276b2f1c0, documentdatadb, 262152 = 10
>mdb_dbi_open: 0x559276b2f1c0, indexingleveldb, 262152 = 11
>mdb_dbi_open: 0x559276b2f1c0, failediddb, 262152 = 12
>mdb_dbi_open: 0x559276b2f1c0, mtimedb, 262204 = 13
>mdb_txn_commit: 0x559276b2f1c0
>mdb_put: 0x5638e7e58130, 3, 3[747874], 91570, 0
>mdb_put: 0x5638e7e58130, 2, 2[6368], 464, 0
>mdb_put: 0x5638e7e58130, 3, 2[6368], 1286, 0
>mdb_put: 0x5638e7e58130, 2, 7[766172696f7573], 1440, 0
>mdb_put: 0x5638e7e58130, 3, 7[766172696f7573], 2282, 0

In the middle of txn 0x5638e7e58130 the init sequence occurs again, and all of the contents of this logfile are only being written by a single process. That means baloo_file has opened the same env twice in the same process, which is explicitly forbidden by the LMDB docs. http://www.lmdb.tech/doc/

Going to close this ticket as Invalid, it's a KDE bug and not an LMDB bug.

(In reply to Howard Chu from comment #178)
> ... Thanks to assistance from another user, we've made some progress setting up
> a KDE test environment to reproduce this issue. Using the replay logging ...
I'd say it's impressive that this has not been forgotten. Very many thanks!

Does this mean that there will be a way of logging writes so that we can troubleshoot any future cases? Baloo has changed quite a lot since this original report; maybe this bug is history, maybe it will reappear. It would be good to have a way of tracking what's happening at the DB level.

Thank you again!

The logging in the branch I referred to here https://git.openldap.org/hyc/openldap/-/tree/mplay09?ref_type=heads is only available when LMDB is compiled with -DMDB_DEBUG, and I haven't decided whether to actually merge that branch into a release or not. I suppose we may as well merge it, since it has no impact if MDB_DEBUG is not defined.

(In reply to Howard Chu from comment #180)
> ... I suppose we may as well merge it, since it has no impact if MDB_DEBUG is not defined ...
We'd need to run Baloo with a specially compiled LMDB to get the trace?

Yes, all the same, I can provide "Gentle Words of Encouragement" for the merge and many thanks to your "additional user". The more tools we have to troubleshoot, the better :-)

(In reply to tagwerk19 from comment #181)
> (In reply to Howard Chu from comment #180)
> > ... I suppose we may as well merge it, since it has no impact if MDB_DEBUG is not defined ...
> We'd need to run Baloo with a specially compiled LMDB to get the trace?

Yes. But that's easily done, just set LD_LIBRARY_PATH to pick up your debug build.
 
> Yes, all the same, I can provide "Gentle Words of Encouragement" for the
> merge and many thanks to your "additional user". The more tools we have to
> troubleshoot, the better :-)

Yeah, it will probably go into the next official release. But at this point there's not much else for us to do,
baloo is clearly breaking LMDB's writer lock. https://bugs.openldap.org/show_bug.cgi?id=9378#c18

I had an issue similar to this recently, tell me if you need more traces

coredumpctl dump
           PID: 1495228 (baloo_file)
           UID: 1000 (geex)
           GID: 1000 (geex)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-01-11 01:46:59 CET (14h ago)
  Command Line: /usr/libexec/kf6/baloo_file
    Executable: /usr/libexec/kf6/baloo_file
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-baloo_file-1495228.scope
          Unit: user@1000.service
     User Unit: app-gnome-baloo_file-1495228.scope
         Slice: user-1000.slice
     Owner UID: 1000 (geex)
       Boot ID: 52ca0d584d194ccbbaa6db5f7762a1d6
    Machine ID: 0d084b96342343d6b1e021c0813ecb22
      Hostname: x2.local
       Storage: /var/lib/systemd/coredump/core.baloo_file.1000.52ca0d584d194ccbbaa6db5f7762a1d6.1495228.1704934019000000.zst (present)
  Size on Disk: 711.9K
       Message: Process 1495228 (baloo_file) of user 1000 dumped core.
                
                Stack trace of thread 1495501:
                #0  0x00007f4d460b33cc __pthread_kill_implementation (libc.so.6 + 0x853cc)
                #1  0x00007f4d460648b2 raise (libc.so.6 + 0x368b2)
                #2  0x00007f4d46f31967 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x5967)
                #3  0x00007f4d46064960 __restore_rt (libc.so.6 + 0x36960)
                #4  0x00007f4d460b33cc __pthread_kill_implementation (libc.so.6 + 0x853cc)
                #5  0x00007f4d460648b2 raise (libc.so.6 + 0x368b2)
                #6  0x00007f4d46050464 abort (libc.so.6 + 0x22464)
                #7  0x00007f4d454ee15a mdb_assert_fail.constprop.0 (liblmdb.so.0.0.0 + 0x415a)
                #8  0x00007f4d454ee1b7 mdb_page_dirty.cold (liblmdb.so.0.0.0 + 0x41b7)
                #9  0x00007f4d454f2b76 mdb_page_alloc.isra.0 (liblmdb.so.0.0.0 + 0x8b76)
                #10 0x00007f4d454f2d9b mdb_page_touch (liblmdb.so.0.0.0 + 0x8d9b)
                #11 0x00007f4d454f4634 mdb_cursor_touch (liblmdb.so.0.0.0 + 0xa634)
                #12 0x00007f4d454f7ac0 mdb_cursor_put (liblmdb.so.0.0.0 + 0xdac0)
                #13 0x00007f4d454fa49f mdb_put (liblmdb.so.0.0.0 + 0x1049f)
                #14 0x00007f4d46d3bf5d _ZN5Baloo10DocumentDB3putEyRK5QListI10QByteArrayE (libKF6BalooEngine.so.6 + 0xff5d)
                #15 0x00007f4d46d55bd5 _ZN5Baloo16WriteTransaction15replaceDocumentERKNS_8DocumentE6QFlagsINS_17DocumentOperationEE (libKF6BalooEngine.so.6 + 0x29bd5)
                #16 0x0000000000416c93 _ZN5Baloo20UnindexedFileIndexer3runEv (baloo_file + 0x16c93)
                #17 0x00007f4d468dee45 _ZN17QThreadPoolThread3runEv (libQt6Core.so.6 + 0x2dee45)
                #18 0x00007f4d468da337 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2da337)
                #19 0x00007f4d460b18da start_thread (libc.so.6 + 0x838da)
                #20 0x00007f4d4612d48c __clone3 (libc.so.6 + 0xff48c)
                
                Stack trace of thread 1495228:
                #0  0x00007f4d4612051f __poll (libc.so.6 + 0xf251f)
                #1  0x00007f4d453ad7af g_main_context_iterate_unlocked.constprop.0 (libglib-2.0.so.0 + 0x587af)
                #2  0x00007f4d453adeac g_main_context_iteration (libglib-2.0.so.0 + 0x58eac)
                #3  0x00007f4d469dfddc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3dfddc)
                #4  0x00007f4d46781833 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x181833)
                #5  0x00007f4d4677e1d4 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x17e1d4)
                #6  0x000000000040c0e2 main (baloo_file + 0xc0e2)
                #7  0x00007f4d460516b7 __libc_start_call_main (libc.so.6 + 0x236b7)
                #8  0x00007f4d46051775 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x23775)
                #9  0x000000000040c201 _start (baloo_file + 0xc201)
                
                Stack trace of thread 1495328:
                #0  0x00007f4d4612051f __poll (libc.so.6 + 0xf251f)
                #1  0x00007f4d453ad7af g_main_context_iterate_unlocked.constprop.0 (libglib-2.0.so.0 + 0x587af)
                #2  0x00007f4d453adeac g_main_context_iteration (libglib-2.0.so.0 + 0x58eac)
                #3  0x00007f4d469dfddc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3dfddc)
                #4  0x00007f4d46781833 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x181833)
                #5  0x00007f4d46874efc _ZN7QThread4execEv (libQt6Core.so.6 + 0x274efc)
                #6  0x00007f4d46c9b4ea _ZN22QDBusConnectionManager3runEv (libQt6DBus.so.6 + 0x354ea)
                #7  0x00007f4d468da337 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2da337)
                #8  0x00007f4d460b18da start_thread (libc.so.6 + 0x838da)
                #9  0x00007f4d4612d48c __clone3 (libc.so.6 + 0xff48c)
                ELF object binary architecture: AMD x86-64

(In reply to Guillaume B. from comment #183)
> I had an issue similar to this recently, tell me if you need more traces

There's nothing for anyone else to do for now. baloo needs to be fixed to stop deleting the lockfile on active LMDB databases.

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/193

*** Bug 481370 has been marked as a duplicate of this bug. ***

*** Bug 478539 has been marked as a duplicate of this bug. ***

*** Bug 474840 has been marked as a duplicate of this bug. ***

*** Bug 473970 has been marked as a duplicate of this bug. ***

*** Bug 481616 has been marked as a duplicate of this bug. ***

Git commit 15083afb9671ec79eb2dbee4ef41a92556d154af by Christoph Cullmann.
Committed on 07/04/2024 at 14:22.
Pushed by cullmann into branch 'master'.

Don't kill the lock file, can lead to random corruption

If a process that writes the database is still running,
like an existing baloo_file_extractor, and one starts a new instance
of baloo_file, that one will remove the lock and now
two writers will use the same database without proper locking.

M  +0    -4    src/file/main.cpp

https://invent.kde.org/frameworks/baloo/-/commit/15083afb9671ec79eb2dbee4ef41a92556d154af

*** Bug 485019 has been marked as a duplicate of this bug. ***