Bug 489048 - Baloo crashes at startup and multiple times after
Summary: Baloo crashes at startup and multiple times after
Status: RESOLVED DUPLICATE of bug 478180
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (other bugs)
Version First Reported In: 5.115.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-06-23 13:24 UTC by Johannes
Modified: 2024-06-25 05:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes 2024-06-23 13:24:32 UTC
Application: baloo_file_extractor (5.115.0)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-35-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 24.04 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Baloo crashes at startup and multiple times after. First time at startup, I was greeted by the crash report even before my backgroud image showed up. Then periodically every few minutes I get a notification for an addition crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Extracteur de fichiers Baloo (baloo_file_extractor), signal: Segmentation fault

[KCrash Handler]
#4  0x00007e456625adb9 in _opf_label_get_by_lang () from /lib/libepub.so.0
#5  0x00007e456625aeb9 in epub_tit_next () from /lib/libepub.so.0
#6  0x00007e4566293178 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so
#7  0x00005645452f41df in ?? ()
#8  0x00005645452f6235 in ?? ()
#9  0x00007e456bb171aa in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007e456bb0624b in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007e456bad8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007e456bb345ab in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007e456bb34f11 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007e456a5145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007e456a573717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007e456a513a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007e456bb35279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007e456bad6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007e456badf3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00005645452ebf63 in ?? ()
#21 0x00007e456b02a1ca in __libc_start_call_main (main=main@entry=0x5645452eb280, argc=argc@entry=1, argv=argv@entry=0x7ffdfa36a4f8) at ../sysdeps/nptl/libc_start_call_main.h:58
#22 0x00007e456b02a28b in __libc_start_main_impl (main=0x5645452eb280, argc=1, argv=0x7ffdfa36a4f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdfa36a4e8) at ../csu/libc-start.c:360
#23 0x00005645452ec075 in ?? ()
[Inferior 1 (process 10342) detached]

The reporter indicates this bug may be a duplicate of or related to bug 481013, bug 481370, bug 481429, bug 481616, bug 483373, bug 484053, bug 485071, bug 487481, bug 488759.

Reported using DrKonqi
Comment 1 tagwerk19 2024-06-23 14:32:25 UTC
(In reply to Johannes from comment #0)
> #6  0x00007e4566293178 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so
This looks like Bug 478180 or Bug 466540, that is either a corrupt .epub or one that include some extrastuff that the extractor cannot cope with. From Bug 478180, if you can find which file Baloo is stumbling on, you can try validating it:
> https://www.w3.org/publishing/epubcheck/
Comment 2 tagwerk19 2024-06-25 05:46:53 UTC

*** This bug has been marked as a duplicate of bug 478180 ***