Bug 496629 - Balloo File Extractor Crashes
Summary: Balloo File Extractor Crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.115.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-11-24 02:41 UTC by Tom
Modified: 2024-12-26 03:47 UTC (History)
2 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 Tom 2024-11-24 02:41:02 UTC
Application: baloo_file_extractor (5.115.0)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-49-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04.1 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Balloo File Extractor Crashes at any point using the system without warning. I restart Balloo but it continues to crash.  Even after a complete system restart it continues to crash.

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  0x000072ba89f85291 in ?? () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#5  0x000072ba89f7aabf in Baloo::PositionDB::get(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#6  0x000072ba89f88627 in Baloo::WriteTransaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x000072ba89f7def1 in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00005eae9b5e315c in ?? ()
#9  0x000072ba893171aa in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x000072ba8930624b in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x000072ba892d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000072ba893345ab in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000072ba89334ed9 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x000072ba881145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x000072ba88173717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x000072ba88113a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x000072ba89335279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000072ba892d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x000072ba892df3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00005eae9b5d8f63 in ?? ()
#21 0x000072ba8882a1ca in __libc_start_call_main (main=main@entry=0x5eae9b5d8280, argc=argc@entry=1, argv=argv@entry=0x7ffcf2fa6958) at ../sysdeps/nptl/libc_start_call_main.h:58
#22 0x000072ba8882a28b in __libc_start_main_impl (main=0x5eae9b5d8280, argc=1, argv=0x7ffcf2fa6958, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcf2fa6948) at ../csu/libc-start.c:360
#23 0x00005eae9b5d9075 in ?? ()
[Inferior 1 (process 237727) detached]

Reported using DrKonqi
Comment 1 tagwerk19 2024-11-24 07:52:37 UTC
> ... Application: baloo_file_extractor (5.115.0) ...

This is perhaps an old version.

It looks a little like a corruption in the Baloo index so rebooting wouldn't help. The equivalent to the "Turn it off and back on again" in this case is to gather a little patience and reindex (so a "balooctl purge", which should close down Baloo, delete the index and rebuild the index afresh...)

There have been some patches in newer versions to avoid index corruption.
Comment 2 John Kizer 2024-11-26 19:45:02 UTC
Hi - are you able to try the balooctl purge command and see if that stops the recurring issue you're seeing?
Comment 3 Bug Janitor Service 2024-12-11 03:46:36 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-12-26 03:47:37 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.