Bug 472197

Summary: Baloo File Extractor crashes on Wayland login
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Bhibb <brysonsd>
Component: Baloo File DaemonAssignee: baloo-bugs-null
Status: RESOLVED WORKSFORME    
Severity: crash CC: tagwerk19
Priority: NOR Keywords: drkonqi
Version: 5.107.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bhibb 2023-07-12 17:31:32 UTC 
Application: baloo_file_extractor (5.107.0)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.3.11-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (Workstation Edition)
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
Baloo File Extractor crashes on Wayland login.

Steps to repro:
1. Boot up system
2. Login to Plasma Wayland session
3. Observe KDE crash handler notifying user of Baloo File Extractor crash

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted

[KCrash Handler]
#4  0x00007f2b942b0844 in __pthread_kill_implementation () from /lib64/libc.so.6
#5  0x00007f2b9425fabe in raise () from /lib64/libc.so.6
#6  0x00007f2b9424887f in abort () from /lib64/libc.so.6
#7  0x00007f2b947c777a in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0
#8  0x00007f2b947c5833 in mdb_page_dirty.lto_priv[cold] () from /lib64/liblmdb.so.0.0.0
#9  0x00007f2b947d3d5e in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0
#10 0x00007f2b947cae22 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0
#11 0x00007f2b947ccabc in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
#12 0x00007f2b947d1180 in mdb_cursor_del () from /lib64/liblmdb.so.0.0.0
#13 0x00007f2b947d2b28 in mdb_del0 () from /lib64/liblmdb.so.0.0.0
#14 0x00007f2b957263c5 in Baloo::DocumentDB::del(unsigned long long) () from /lib64/libKF5BalooEngine.so.5
#15 0x00007f2b9573f27d in Baloo::WriteTransaction::removeDocument(unsigned long long) () from /lib64/libKF5BalooEngine.so.5
#16 0x00005651facadded in Baloo::App::index(Baloo::Transaction*, QString const&, unsigned long long) ()
#17 0x00005651facaf284 in Baloo::App::processNextFile() ()
#18 0x00007f2b94aeba7a in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5
#19 0x00007f2b94adec8b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#20 0x00007f2b94ab4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#21 0x00007f2b94b05a7b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#22 0x00007f2b94b06379 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#23 0x00007f2b9371348c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#24 0x00007f2b93771638 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#25 0x00007f2b93710b13 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#26 0x00007f2b94b06729 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#27 0x00007f2b94ab2b4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#28 0x00007f2b94abaddb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#29 0x00005651faca505b in main ()
[Inferior 1 (process 7101) detached]

The reporter indicates this bug may be a duplicate of or related to bug 471918, bug 468474, bug 467769, bug 422393, bug 421885, bug 405284, bug 399407.

Reported using DrKonqi
Comment 1 tagwerk19 2023-07-13 16:24:46 UTC 
An initial question...

    Do you also get a crash when you log in with X11? You just mention Wayland, it would be interesting if it crashed in Wayland and not X.

If there's a "immediate" crash on logon, there's a chance of a corrupted index. Igor Poboiko has a consistency check script (in python) here:

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

With a quick description here:

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

It might be worth a try. Heads up about the need to load the whole database into memory

If you've got a corruption, probably your only option is to purge and reindex.
Comment 2 tagwerk19 2023-07-15 06:20:08 UTC 
(In reply to tagwerk19 from comment #1)
> ... a consistency check script (in python) ...
Digging out my notes, I had to:

    $ sudo pkcon install python3-pip
    $ pip install lmdb
    $ wget https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py
    $ chmod 700 baloo-checkdb.py
Comment 3 Bug Janitor Service 2023-07-31 03:44:59 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2023-08-15 03:45:18 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!