Bug 478180

Summary:	Baloo crashes at startup
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	ralph <ralph>
Component:	Baloo File Daemon	Assignee:	baloo-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	korotkovin, lemondejojo, tagwerk19
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.111.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ralph@crutzen.eu 2023-12-06 19:22:06 UTC

Application: baloo_file_extractor (5.111.0)

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.2-201.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 39 (KDE Plasma)
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
Baloo crashes after logging in; that's all I know.

The crash can be reproduced every time.

-- Backtrace:
Application: Bestandextraheerder van baloo (baloo_file_extractor), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fc317e1d609 in _opf_label_get_by_lang () from /lib64/libepub.so.0
#5  0x00007fc317e1d709 in epub_tit_next () from /lib64/libepub.so.0
#6  0x00007fc317e1d983 in epub_get_titerator () from /lib64/libepub.so.0
#7  0x00007fc32432b370 in KFileMetaData::EPubExtractor::extract(KFileMetaData::ExtractionResult*) () from /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so
#8  0x00005603df6901b8 in Baloo::App::index(Baloo::Transaction*, QString const&, unsigned long long) ()
#9  0x00005603df691f84 in Baloo::App::processNextFile() ()
#10 0x00007fc337cebe8a in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5
#11 0x00007fc337cdf09b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007fc337cb4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007fc337d05e2b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#14 0x00007fc337d06761 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#15 0x00007fc336712e5c in g_main_context_dispatch_unlocked.lto_priv () from /lib64/libglib-2.0.so.0
#16 0x00007fc33676ddd8 in g_main_context_iterate_unlocked.isra () from /lib64/libglib-2.0.so.0
#17 0x00007fc336710ad3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007fc337d06ad9 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007fc337cb2f5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007fc337cbb1eb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#21 0x00005603df68805b in main ()
[Inferior 1 (process 3292) detached]

Reported using DrKonqi

Comment 1 tagwerk19 2023-12-06 21:52:00 UTC

(In reply to ralph@crutzen.eu from comment #0)
> ...
> #5  0x00007fc317e1d709 in epub_tit_next () from /lib64/libepub.so.0
> #6  0x00007fc317e1d983 in epub_get_titerator () from /lib64/libepub.so.0
> #7  0x00007fc32432b370 in KFileMetaData::EPubExtractor::extract(KFileMetaData::ExtractionResult*) ()
>     from /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so
> ...
This suggests the extractor is failing on an epub. You might be able to find which it it with
    balooctl failed
or run 
    balooctl monitor
restart baloo with
    systemctl --user restart kde-baloo
and watch the files as they are indexed,

If you can find which file it is, you can see if you can validate it.
    https://www.w3.org/publishing/epubcheck/

Comment 2 ralph@crutzen.eu 2023-12-08 08:14:47 UTC

Thanks! I removed the epub file.

Comment 3 tagwerk19 2023-12-09 10:16:25 UTC

(In reply to ralph@crutzen.eu from comment #2)
> Thanks! I removed the epub file.
If you've got an .epub that you can share (as a link?) that is causing the extractor to crash, it's worth sharing :-) Other people may be hitting the same problem.

Comment 4 tagwerk19 2024-06-25 05:46:53 UTC

*** Bug 489048 has been marked as a duplicate of this bug. ***

Comment 5 tagwerk19 2024-08-17 14:26:56 UTC

*** Bug 481013 has been marked as a duplicate of this bug. ***