Bug 465529 - Baloo file extractor crashes on startup
Summary: Baloo file extractor crashes on startup
Status: RESOLVED DUPLICATE of bug 389848
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.102.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-10 01:49 UTC by Natalie Clarius
Modified: 2023-05-18 16:20 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.34 KB, text/plain)
2023-03-22 15:40 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Natalie Clarius 2023-02-10 01:49:13 UTC
Since I did a system upgrade a week or so ago, baloo_file_extractor crashes on every system startup with the following backtrace:

Application: baloo_file_extractor (baloo_file_extractor), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x00007fe0b4afa6b3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#8  0x00007fe0b4aaa938 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#9  0x00007fe0b4a9453d in __GI_abort () at abort.c:79
#10 0x00007fe0b3931624 in ?? () from /usr/lib/liblmdb.so
#11 0x00007fe0b3925185 in ?? () from /usr/lib/liblmdb.so
#12 0x00007fe0b3927716 in ?? () from /usr/lib/liblmdb.so
#13 0x00007fe0b3927963 in ?? () from /usr/lib/liblmdb.so
#14 0x00007fe0b392953c in ?? () from /usr/lib/liblmdb.so
#15 0x00007fe0b392c78e in mdb_cursor_put () from /usr/lib/liblmdb.so
#16 0x00007fe0b392f64b in mdb_put () from /usr/lib/liblmdb.so
#17 0x00007fe0b4c8a4bf in Baloo::PositionDB::put (this=<optimized out>, term=..., list=...) at /usr/src/debug/baloo/baloo-5.102.0/src/engine/positiondb.cpp:69
#18 0x00007fe0b4c996a3 in Baloo::WriteTransaction::commit (this=<optimized out>) at /usr/src/debug/baloo/baloo-5.102.0/src/engine/writetransaction.cpp:319
#19 0x00007fe0b4c8df7e in Baloo::Transaction::commit (this=0x555e98706e80) at /usr/src/debug/baloo/baloo-5.102.0/src/engine/transaction.cpp:272
#20 0x0000555e975eb08d in Baloo::App::processNextFile (this=0x7fffa3d97940) at /usr/src/debug/baloo/baloo-5.102.0/src/file/extractor/app.cpp:109
#21 0x00007fe0b40c1387 in QtPrivate::QSlotObjectBase::call (a=<optimized out>, r=<optimized out>, this=<optimized out>, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 QSingleShotTimer::timerEvent (this=0x555e98d586d0) at kernel/qtimer.cpp:320
#23 0x00007fe0b40b1b56 in QObject::event (this=0x555e98d586d0, e=0x7fffa3d97590) at kernel/qobject.cpp:1324
#24 0x00007fe0b408df48 in QCoreApplication::notifyInternal2 (receiver=0x555e98d586d0, event=0x7fffa3d97590) at kernel/qcoreapplication.cpp:1064
#25 0x00007fe0b40d84b3 in QTimerInfoList::activateTimers (this=0x555e98721290) at kernel/qtimerinfo_unix.cpp:643
#26 0x00007fe0b40d8af2 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#27 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:230
#28 0x00007fe0b2f1682b in g_main_dispatch (context=0x7fe0a8005010) at ../glib/glib/gmain.c:3454
#29 g_main_context_dispatch (context=0x7fe0a8005010) at ../glib/glib/gmain.c:4172
#30 0x00007fe0b2f6dcc9 in g_main_context_iterate.constprop.0 (context=0x7fe0a8005010, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4248
#31 0x00007fe0b2f150e2 in g_main_context_iteration (context=0x7fe0a8005010, may_block=1) at ../glib/glib/gmain.c:4313
#32 0x00007fe0b40d8c6c in QEventDispatcherGlib::processEvents (this=0x555e98717a30, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33 0x00007fe0b40866ec in QEventLoop::exec (this=0x7fffa3d97840, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x00007fe0b4091219 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x0000555e975e0cf4 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/baloo/baloo-5.102.0/src/file/extractor/main.cpp:37
[Inferior 1 (process 1835) detached]

System info:
Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.9-arch1-1 (64-bit)
Comment 1 tagwerk19 2023-02-10 08:27:34 UTC
Maybe you can get something from Igor Poboiko's "baloo-checkdb.py" script:

        https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py

As posted here:

        https://invent.kde.org/frameworks/baloo/-/merge_requests/87

I've only tried it on test systems with small indexes (for example Bug 464226). I think baloo has been missing consistency check code, nice that this has been posted. Not tried with large data though, you could need patience.

Would also be interesting to know what filesystem you are running on; whether BTRFS or not...
Comment 2 Natalie Clarius 2023-02-11 14:17:49 UTC
Thanks for the hint!

File system is ext4.

Running the script gives me a ~75k line output with many entries of the following form:

- ERROR: corrupted b'docterms' entry for 43924609061421827 (/home/natalie/OneDrive/Lit/Logic/Lambda-Combinators-Functions/FormLang/Hillebrand-Kanellakis_1996_STLC-expressive-power.pdf)
- ERROR: 41815071449481987 (/???/README) has dangling parent 42187552488227587 (/???)
- WARNING: following documents were not found in idfilename:
 - 42187552488227587 (/???)
-  ERROR: 17451753498804995 (/home/natalie/OneDrive/Lit/Logic/ModLog/Chellas_1980_Modal-logic.pdf) has term T5 which wasn't found in PostingDB
- WARNING: term Fbussproofs points to unknown document 1103817739642 (/???)

So it seems the database is screwed up. I'm going to try purging and rebuilding the index.
Comment 3 Nate Graham 2023-02-12 22:35:51 UTC

*** This bug has been marked as a duplicate of bug 389848 ***
Comment 4 Chris 2023-03-22 15:40:10 UTC
Created attachment 157516 [details]
New crash information added by DrKonqi

baloo_file_extractor (5.104.0) using Qt 5.15.8

Every time I start my system up, baloo_file_extractor crashes.

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140477036886336) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140477036886336) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140477036886336, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x00007fc35d242476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fc35d2287f3 in __GI_abort () at ./stdlib/abort.c:79