Description of problem: Expected to be identical to what https://bugs.kde.org/show_bug.cgi?id=484548#c0 describes. Version-Release number of selected component: kf6-baloo-file-6.0.0-3.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: baloo_file killed by SIGABRT journald_cursor: s=efcd76593cb5498f888fdc929380cfaa;i=559a;b=f5ffd89df9f94695b6a8d6ee96a70bb9;m=9ef398c8;t=614952d87f4e2;x=12cf9a1350ad1d62 executable: /usr/libexec/kf6/baloo_file cmdline: /usr/libexec/kf6/baloo_file cgroup: 0::/user.slice/user-1000.slice/user/background.slice/kde-baloo.service rootdir: / uid: 1000 kernel: 6.8.1-300.fc40.x86_64 package: kf6-baloo-file-6.0.0-3.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: KInotify::slotEvent comment: https://bugs.kde.org/show_bug.cgi?id=484548#c0 Truncated backtrace: Thread no. 1 (17 frames) #13 KInotify::slotEvent at /usr/src/debug/kf6-baloo-6.0.0-3.fc40.x86_64/src/file/kinotify.cpp:300 #14 QtPrivate::QSlotObjectBase::call at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:433 #15 doActivate<false> at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:4039 #16 QMetaObject::activate at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:4099 #17 QSocketNotifier::activated at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/redhat-linux-build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:231 #18 QSocketNotifier::event at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qsocketnotifier.cpp:326 #19 doNotify at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1217 #20 QCoreApplication::notify at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1200 #21 QCoreApplication::notifyInternal2 at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121 #22 QCoreApplication::sendEvent at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539 #23 socketNotifierSourceDispatch at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:73 #25 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152 #26 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217 #27 g_main_context_iteration at ../glib/gmain.c:4282 #28 QEventDispatcherGlib::processEvents at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #29 QEventLoop::exec at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/global/qflags.h:34 #30 QCoreApplication::exec at /usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/global/qflags.h:74
Created attachment 2023698 [details] File: proc_pid_status
Created attachment 2023699 [details] File: maps
Created attachment 2023700 [details] File: limits
Created attachment 2023701 [details] File: environ
Created attachment 2023702 [details] File: open_fds
Created attachment 2023703 [details] File: mountinfo
Created attachment 2023704 [details] File: os_info
Created attachment 2023705 [details] File: cpuinfo
Created attachment 2023706 [details] File: core_backtrace
Created attachment 2023707 [details] File: dso_list
Created attachment 2023708 [details] File: var_log_messages
Created attachment 2023709 [details] File: backtrace
You seem to be getting different crashes all around malloc/free calls. Can you try running baloo in valgrind and share the results? Something like `systemctl --user stop kde-baloo` then `valgrind --track-origins=yes /usr/libexec/kf6/baloo_file`
Created attachment 2025671 [details] Valgrind output for #c13. (In reply to Alessandro Astone from comment #13) > You seem to be getting different crashes all around malloc/free calls. > > Can you try running baloo in valgrind and share the results? > Something like `systemctl --user stop kde-baloo` then `valgrind > --track-origins=yes /usr/libexec/kf6/baloo_file` ales.astone, I've invoked "systemctl --user stop kde-baloo && valgrind --track-origins=yes /usr/libexec/kf6/baloo_file" and attached a log file. Your command appeared to provide some useful output - it certainly provided some kind of trace. Thanks for making it easy for me.
Mh, can you try adding `--error-limit=no`?
(In reply to Alessandro Astone from comment #15) > Mh, can you try adding `--error-limit=no`? I'm doing so now. However, it never seems to end by itself. This is the first time I've Valgrind, so am I meant to ^C it when it seems like I've captured something useful, or am I meant to wait for it to capture by itself and then prompt me, like gdb does for a bt?
You'll have to manually stop it after some time
Created attachment 2025684 [details] Huge valgrind output. (In reply to Alessandro Astone from comment #17) > You'll have to manually stop it after some time
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.