Bug 470326 - Baloo crashed
Summary: Baloo crashed
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.106.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-05-27 09:24 UTC by vvs170
Modified: 2023-12-10 03:46 UTC (History)
3 users (show)

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


Attachments
New crash information added by DrKonqi (21.49 KB, text/plain)
2023-10-21 12:55 UTC, aronkvh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vvs170 2023-05-27 09:24:17 UTC
Application: baloo_file_extractor (5.106.0)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Baloo crashed after booting the computer with the restoration of the session.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Служба извлечения информации для поиска в подсистеме Baloo (baloo_file_extractor), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  __memcmp_avx2_movbe () at ../sysdeps/x86_64/multiarch/memcmp-avx2-movbe.S:415
#7  0x00007f727a9411f0 in qstrcmp (str1=..., str2=...) at text/qbytearray.cpp:506
#8  0x00007f727b5f9e18 in operator< (a2=..., a1=...) at /usr/include/qt/QtCore/qbytearray.h:697
#9  qMapLessThanKey<QByteArray> (key2=..., key1=...) at /usr/include/qt/QtCore/qmap.h:68
#10 QMapNode<QByteArray, Baloo::Document::TermData>::lowerBound (akey=..., this=<optimized out>) at /usr/include/qt/QtCore/qmap.h:153
#11 QMapData<QByteArray, Baloo::Document::TermData>::findNode (this=<optimized out>, akey=...) at /usr/include/qt/QtCore/qmap.h:288
#12 QMap<QByteArray, Baloo::Document::TermData>::operator[] (akey=..., this=0x7ffd96eae030) at /usr/include/qt/QtCore/qmap.h:681
#13 Baloo::Document::addPositionTerm (this=0x7ffd96eae020, term=..., position=77447) at /usr/src/debug/baloo/baloo-5.106.0/src/engine/document.cpp:24
#14 0x00007f727b608967 in Baloo::TermGenerator::indexText (this=0x7ffd96eae078, text=..., prefix=...) at /usr/src/debug/baloo/baloo-5.106.0/src/engine/termgenerator.cpp:111
#15 0x00007f727b608a5a in Baloo::TermGenerator::indexText (this=<optimized out>, text=...) at /usr/src/debug/baloo/baloo-5.106.0/src/engine/termgenerator.cpp:51
#16 0x00007f727551d6f5 in KFileMetaData::PopplerExtractor::extract (this=<optimized out>, result=0x7ffd96eae010) at /usr/src/debug/kfilemetadata/kfilemetadata-5.106.0/src/extractors/popplerextractor.cpp:85
#17 0x0000556abc78c499 in Baloo::App::index (this=this@entry=0x7ffd96eae6e0, tr=0x7f72700112a0, url=..., id=id@entry=1008870835529713713) at /usr/src/debug/baloo/baloo-5.106.0/src/file/extractor/app.cpp:170
#18 0x0000556abc78e24e in Baloo::App::processNextFile (this=0x7ffd96eae6e0) at /usr/src/debug/baloo/baloo-5.106.0/src/file/extractor/app.cpp:102
#19 0x00007f727aac2834 in QObject::event (this=0x7ffd96eae6e0, e=0x556abfb93f40) at kernel/qobject.cpp:1347
#20 0x00007f727aa9ab18 in QCoreApplication::notifyInternal2 (receiver=0x7ffd96eae6e0, event=0x556abfb93f40) at kernel/qcoreapplication.cpp:1064
#21 0x00007f727aa9fa7b in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x556abd7ddbb0) at kernel/qcoreapplication.cpp:1821
#22 0x00007f727aae6088 in postEventSourceDispatch (s=0x556abd89ddc0) at kernel/qeventdispatcher_glib.cpp:277
#23 0x00007f7279510981 in g_main_dispatch (context=0x7f7270000ee0) at ../glib/glib/gmain.c:3460
#24 g_main_context_dispatch (context=0x7f7270000ee0) at ../glib/glib/gmain.c:4200
#25 0x00007f727956db39 in g_main_context_iterate.isra.0 (context=context@entry=0x7f7270000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4276
#26 0x00007f727950e032 in g_main_context_iteration (context=0x7f7270000ee0, may_block=1) at ../glib/glib/gmain.c:4343
#27 0x00007f727aae9f0c in QEventDispatcherGlib::processEvents (this=0x556abd897860, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x00007f727aa99824 in QEventLoop::exec (this=this@entry=0x7ffd96eae5d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x00007f727aa9acc3 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x00007f727af3b7c2 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870
#31 0x0000556abc783d4e in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/baloo/baloo-5.106.0/src/file/extractor/main.cpp:43
[Inferior 1 (process 2771) detached]

Reported using DrKonqi
Comment 1 aronkvh 2023-10-21 12:55:52 UTC
Created attachment 162475 [details]
New crash information added by DrKonqi

baloo_file_extractor (5.111.0) using Qt 5.15.11

Crash loop after turning on the device, I didn't use search or dolphin yet

-- Backtrace (Reduced):
#6  __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:32
#7  0x00007fa7d86d9338 in FindNode () from /lib/libepub.so.0
#8  0x00007fa7d86d8009 in _opf_manifest_get_by_id () from /lib/libepub.so.0
#9  0x00007fa7d86d51bd in _get_spine_it_url () from /lib/libepub.so.0
#10 0x00007fa7d86d5262 in epub_it_get_curr () from /lib/libepub.so.0
Comment 2 tagwerk19 2023-10-21 15:02:28 UTC
(In reply to aronkvh from comment #1)
> #7  0x00007fa7d86d9338 in FindNode () from /lib/libepub.so.0
> #8  0x00007fa7d86d8009 in _opf_manifest_get_by_id () from /lib/libepub.so.0
> #9  0x00007fa7d86d51bd in _get_spine_it_url () from /lib/libepub.so.0
> #10 0x00007fa7d86d5262 in epub_it_get_curr () from /lib/libepub.so.0
If you can find the "suspect" .epub file, you can perhaps check it with the ePub validator:
    https://www.w3.org/publishing/epubcheck/
There is (or was?) a flatpak but I don't seem to be able to find it at the moment.

It's possible that you can catch the "failing" file if you follow the content indexing with "balooctl monitor" or try to set up logging - Bug 460390 and:
    https://bugs.kde.org/show_bug.cgi?id=460390#c2
Comment 3 tagwerk19 2023-10-26 07:10:59 UTC
(In reply to vvs170 from comment #0)
> #16 0x00007f727551d6f5 in KFileMetaData::PopplerExtractor::extract (this=<optimized out>, result=0x7ffd96eae010) at /usr/src/debug/kfilemetadata/kfilemetadata-5.106.0/src/extractors/popplerextractor.cpp:85
Sorry, missed the fact that the original failed in a different place...

PopplerExtractor would be called when trying to index a PDF. Try "balooctl monitor" and see what file is triggering the crash..
Comment 4 Stefan Brüns 2023-11-10 14:41:40 UTC
(In reply to aronkvh from comment #1)
> Created attachment 162475 [details]
> New crash information added by DrKonqi
> 
> baloo_file_extractor (5.111.0) using Qt 5.15.11
> 
> Crash loop after turning on the device, I didn't use search or dolphin yet
> 
> -- Backtrace (Reduced):
> #6  __strcmp_sse2_unaligned () at
> ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:32
> #7  0x00007fa7d86d9338 in FindNode () from /lib/libepub.so.0
> #8  0x00007fa7d86d8009 in _opf_manifest_get_by_id () from /lib/libepub.so.0
> #9  0x00007fa7d86d51bd in _get_spine_it_url () from /lib/libepub.so.0
> #10 0x00007fa7d86d5262 in epub_it_get_curr () from /lib/libepub.so.0

This is unrelated.

Note, many distributions ship a known buggy version of libepub/ebook-tools. openSUSE uses a known fixed and maintained version, for others please use the distribution bugtracker.
Comment 5 Stefan Brüns 2023-11-10 14:42:25 UTC
Missing response from reporter, no reproducer.
Comment 6 Bug Janitor Service 2023-11-25 03:45:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-12-10 03:46:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!