https://bugs.kde.org/show_bug.cgi?id=409127
--- Comment #1 from Loïc Grobol <loic.gro...@gmail.com> --- Created attachment 121125 --> https://bugs.kde.org/attachment.cgi?id=121125&action=edit New crash information added by DrKonqi baloo_file (5.59.0) using Qt 5.12.2 - What I was doing when the application crashed: This time it happened directly at startup -- Backtrace (Reduced): #6 0x00007f811ad6cce0 in mdb_xcursor_init1 (node=node@entry=0x7f41169bbc34, mc=<optimized out>, mc=<optimized out>) at mdb.c:7543 #7 0x00007f811ad703e0 in mdb_cursor_next (mc=mc@entry=0x7f4108034410, key=0x7f8116c93ab0, data=data@entry=0x0, op=MDB_NEXT) at mdb.c:5925 #8 0x00007f811ad6ee73 in mdb_cursor_get (mc=0x7f4108034410, key=key@entry=0x7f8116c93ab0, data=data@entry=0x0, op=op@entry=MDB_NEXT) at mdb.c:6441 #9 0x00007f811c82e0ae in Baloo::DocumentIdDB::fetchItems (this=this@entry=0x7f8116c93b30, size=size@entry=40) at ./src/engine/documentiddb.cpp:126 #10 0x00007f811c845c11 in Baloo::Transaction::fetchPhaseOneIds (this=this@entry=0x7f8116c93b70, size=size@entry=40) at ./src/engine/transaction.cpp:183 -- You are receiving this mail because: You are watching all bug changes.