Created attachment 142257 [details] drkonqi crash report file SUMMARY baloo_file can segfault during background operations during system idle time. Note that this throws different traces than bug 443226, previously reported crash by me for baloo_file, but generates different signal and has different trace. Uncertain if it is related or not. If it is a duplicate, can repost this different trace in that bug instead. STEPS TO REPRODUCE 1. Leave computer unattended for extended period of time (amount unknown) OBSERVED RESULT baloo_file segfaults. EXPECTED RESULT baloo_file does not segfault. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Hardware: CPU: Ryzen 3950X GPU: AMD 5700 XT RAM: 32GB ECC 3200 MHz, JDEC default timings Motherboard: ASrock x570 Creator OS Drive: Corsair Force Series MP600 2TB NVMe Note, system is dual boot with Win10. baloo-kf5/hirsute,now 5.86.0-0ubuntu1~ubuntu21.04~ppa1 System is set up to get updates from the kbuntu updates and backports PPAs. Backtrace: Application: baloo_file (baloo_file), signal: Segmentation fault [KCrash Handler] #4 QString::QString (other=..., this=<optimized out>, this=<optimized out>, other=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093 #5 QList<QString>::node_copy (src=0x55820a5ef588, to=0x7f9ba9e67480 <QListData::shared_null+16>, from=<optimized out>, this=0x558202c0a650) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:505 #6 QList<QString>::detach_helper_grow(int, int) [clone .constprop.0] (this=0x558202c0a650, c=c@entry=1, i=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:813 #7 0x0000558201e7b9dc in QList<QString>::append (this=<optimized out>, t=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:623 #8 0x0000558201e82b31 in Baloo::FileContentIndexer::slotFinishedIndexingFile (this=0x558202c0a610, filePath=..., fileUpdated=<optimized out>) at ./src/file/filecontentindexer.cpp:125 #9 0x00007f9ba9da810c in QObject::event (this=0x558202c0a610, e=0x7f5b90075810) at kernel/qobject.cpp:1314 #10 0x00007f9ba9d7a78f in doNotify (event=0x7f5b90075810, receiver=0x558202c0a610) at kernel/qcoreapplication.cpp:1153 #11 QCoreApplication::notify (event=<optimized out>, receiver=<optimized out>, this=<optimized out>) at kernel/qcoreapplication.cpp:1139 #12 QCoreApplication::notifyInternal2 (receiver=0x558202c0a610, event=0x7f5b90075810) at kernel/qcoreapplication.cpp:1063 #13 0x00007f9ba9d7d7e1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x558202bd04b0) at kernel/qcoreapplication.cpp:1817 #14 0x00007f9ba9dd4ba7 in postEventSourceDispatch (s=0x558202beec70) at kernel/qeventdispatcher_glib.cpp:277 #15 0x00007f9ba83018eb in g_main_dispatch (context=0x558202bec9b0) at ../../../glib/gmain.c:3337 #16 g_main_context_dispatch (context=0x558202bec9b0) at ../../../glib/gmain.c:4055 #17 0x00007f9ba8354d28 in g_main_context_iterate.constprop.0 (context=context@entry=0x558202bec9b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4131 #18 0x00007f9ba82ff023 in g_main_context_iteration (context=0x558202bec9b0, may_block=may_block@entry=1) at ../../../glib/gmain.c:4196 #19 0x00007f9ba9dd4204 in QEventDispatcherGlib::processEvents (this=0x558202bec030, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x00007f9ba9d7911b in QEventLoop::exec (this=this@entry=0x7ffcee176e20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #21 0x00007f9ba9d81604 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #22 0x0000558201e778aa in main (argc=<optimized out>, argv=<optimized out>) at ./src/file/main.cpp:78 [Inferior 1 (process 2538) detached] The reporter indicates this bug may be a duplicate of or related to bug 443226 .
There's no chance that this is an index corruption? I'd suggest to close down baloo, rename the .local/share/baloo/index file, restart and allow baloo to rebuild - and see if the issue reappears.
(In reply to tagwerk19 from comment #1) > There's no chance that this is an index corruption? > > I'd suggest to close down baloo, rename the > .local/share/baloo/index > file, restart and allow baloo to rebuild - and see if the issue reappears. I'll force it to rebuild and get back to you, but it might be inconclusive. It's not frequent by any means.
(In reply to ltstarwarskid from comment #2) > (In reply to tagwerk19 from comment #1) > > There's no chance that this is an index corruption? > > > > I'd suggest to close down baloo, rename the > > .local/share/baloo/index > > file, restart and allow baloo to rebuild - and see if the issue reappears. > > I'll force it to rebuild and get back to you, but it might be inconclusive. > It's not frequent by any means. No crash since forced a rebuild on 10/11, however as noted it is a rare crash for me. The original crash and current lack of it however might also be related to me no longer using the wayland session until a different issue that caused plasmashell and related items to crash is resolved since rebuild.
*** This bug has been marked as a duplicate of bug 441860 ***