Bug 467485 - baloo crash on login
Summary: baloo crash on login
Status: RESOLVED DUPLICATE of bug 389848
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.104.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-03-17 12:26 UTC by Johannes Löbel
Modified: 2023-04-03 23:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Löbel 2023-03-17 12:26:49 UTC
Application: baloo_file_extractor (5.104.0)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.1.19 x86_64
Windowing System: Wayland
Distribution: Slackware 15.0 x86_64 (post 15.0 -current)
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
Every time I login on kde baloo crash.  This happens after an upgrade of the operating system

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007fae166959eb in pthread_kill@@GLIBC_2.34 () from /lib64/libc.so.6
#5  0x00007fae16643d82 in raise () from /lib64/libc.so.6
#6  0x00007fae1662b4a4 in abort () from /lib64/libc.so.6
#7  0x00007fae17aed102 in ?? () from /usr/lib64/liblmdb.so.0.0.0
#8  0x00007fae17aed15f in ?? () from /usr/lib64/liblmdb.so.0.0.0
#9  0x00007fae17af1a76 in ?? () from /usr/lib64/liblmdb.so.0.0.0
#10 0x00007fae17af1c9b in ?? () from /usr/lib64/liblmdb.so.0.0.0
#11 0x00007fae17af3534 in ?? () from /usr/lib64/liblmdb.so.0.0.0
#12 0x00007fae17af6980 in mdb_cursor_put () from /usr/lib64/liblmdb.so.0.0.0
#13 0x00007fae17af935f in mdb_put () from /usr/lib64/liblmdb.so.0.0.0
#14 0x00007fae17b885ec in Baloo::PositionDB::put(QByteArray const&, QVector<Baloo::PositionInfo> const&) () from /usr/lib64/libKF5BalooEngine.so.5
#15 0x00007fae17b9a206 in Baloo::WriteTransaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5
#16 0x00007fae17b91b3f in Baloo::Transaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5
#17 0x000000000040d424 in ?? ()
#18 0x00007fae16eee485 in ?? () from /usr/lib64/libQt5Core.so.5
#19 0x00007fae16edf53d in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#20 0x00007fae16eb5458 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#21 0x00007fae16f08f31 in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#22 0x00007fae16f09704 in ?? () from /usr/lib64/libQt5Core.so.5
#23 0x00007fae15f1dd79 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fae15f1dfe8 in ?? () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fae15f1e06c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#26 0x00007fae16f09a16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#27 0x00007fae16eb403b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#28 0x00007fae16ebbb42 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#29 0x000000000040a40d in ?? ()
#30 0x00007fae1662c6b7 in __libc_start_call_main () from /lib64/libc.so.6
#31 0x00007fae1662c775 in __libc_start_main_impl () from /lib64/libc.so.6
#32 0x000000000040a491 in ?? ()
[Inferior 1 (process 3014) detached]

The reporter indicates this bug may be a duplicate of or related to bug 465529, bug 450988.

Reported using DrKonqi
Comment 1 @WolleSch 2023-03-29 08:06:59 UTC
Baloo crashes regularly when logging in. The crash message offers to restart baloo. After that it works. Anyway

ps -e | grep baloo

executes the following:

1419 ?   00:00:01 baloo_file
1997 ?   00:00:09 baloo_file_extr
2053 ?   00:00:00 baloorunner 

So I assume that baloo is running then. From this point of view, the error message is only annoying.
Comment 2 Nate Graham 2023-04-03 23:13:21 UTC

*** This bug has been marked as a duplicate of bug 389848 ***