https://bugs.kde.org/show_bug.cgi?id=503674

            Bug ID: 503674
           Summary: baloo consistent and repeated crash
    Classification: Frameworks and Libraries
           Product: frameworks-baloo
           Version: 5.115.0
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: Baloo File Daemon
          Assignee: baloo-bugs-n...@kde.org
          Reporter: ryan.e.jo...@gmail.com
  Target Milestone: ---

Application: baloo_file_extractor (5.115.0)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-59-lowlatency x86_64
Windowing System: Wayland
Distribution: Ubuntu 24.04.2 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
After recent update, the baloo extractor crashes with a segmentation fault,
repeatedly. Closing the crash dialog only sees it return a few seconds later.
After the uptime is considerable the crash extractor does not keep appearing,
but the behaviour continues upon restart. No other effects on the system are
noticeable but it would be nice if the warnings would cease.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x000079a81b70ad3c in mdb_midl_xmerge () from
/lib/x86_64-linux-gnu/liblmdb.so.0
#5  0x000079a81b70b669 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#6  0x000079a81b700415 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x000079a81b707779 in mdb_cursor_put () from
/lib/x86_64-linux-gnu/liblmdb.so.0
#8  0x000079a81b7082fe in mdb_put () from /lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x000079a81b8937ee in Baloo::PositionDB::put(QByteArray const&,
QVector<Baloo::PositionInfo> const&) () from
/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x000079a81b8a11c1 in Baloo::WriteTransaction::commit() () from
/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x000079a81b896ef1 in Baloo::Transaction::commit() () from
/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#12 0x00005885ab8fd15c in ?? ()
#13 0x000079a81ad171aa in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x000079a81ad0624b in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x000079a81acd8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x000079a81ad345ab in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x000079a81ad34f11 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000079a8197145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x000079a819773717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x000079a819713a53 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x000079a81ad35279 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000079a81acd6a7b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000079a81acdf3e8 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00005885ab8f2f63 in ?? ()
#25 0x000079a81a22a1ca in __libc_start_call_main
(main=main@entry=0x5885ab8f2280, argc=argc@entry=1,
argv=argv@entry=0x7fff11fe4148) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x000079a81a22a28b in __libc_start_main_impl (main=0x5885ab8f2280, argc=1,
argv=0x7fff11fe4148, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff11fe4138) at ../csu/libc-start.c:360
#27 0x00005885ab8f3075 in ?? ()
[Inferior 1 (process 156375) detached]

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to