| Summary: | baloo_file_extractor crashes on startup | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kfilemetadata | Reporter: | aronkvh |
| Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | stefan.bruens, tagwerk19 |
| Priority: | NOR | ||
| Version First Reported In: | 5.103.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
aronkvh
2023-02-27 16:00:10 UTC
(In reply to aronkvh from comment #0) > baloo_file_extractor crashes and a drkonqi window appears at every boot. > ... > #9 0x00007fd4025150d7 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so > ... I can only guess at this stuff, but that looks as if baloo_file_extractor is failing when trying to get data out of an epub. Do you have epubs in your indexed folders? You might be able to get more details by turning on logging: Create a folder ~/.config/QtProject/ and then a file ~/.config/QtProject/qtlogging.ini that contains [Rules] kf.filemetadata=true kf.baloo=true With that you might (should) see log messages appearing when you check with journalctl 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! It stopped happening after around a week after deleting a faulty .epub file You didn't keep a copy of the corrupt .epub? It shouldn't be that a corrupt file causes baloo (kfilemetadata extractor) to crash... (In reply to tagwerk19 from comment #4) > You didn't keep a copy of the corrupt .epub? > > It shouldn't be that a corrupt file causes baloo (kfilemetadata extractor) > to crash... I managed to find it again: https://bugs.kde.org/attachment.cgi?id=157452 (In reply to aronkvh from comment #5) > I managed to find it again: https://bugs.kde.org/attachment.cgi?id=157452 Oh yes, so it does. Tbanks! Flagging as Confirmed. Looking at the file with epubcheck https://www.w3.org/publishing/epubcheck/ gives a collection of errors (including one fatal) Actually its a bug in the used libepub from ebook-tools. You can also try to open the file with okular, which will also crash. Fix pending on openSUSE (https://build.opensuse.org/request/show/1082236), for any other distribution your mileage may vary. (In reply to Stefan Brüns from comment #8) > Fix pending on openSUSE ... I read that as the "upstream" is not maintained, so it is up to individual distributions to patch their own copies (?) (In reply to tagwerk19 from comment #9) > (In reply to Stefan Brüns from comment #8) > > Fix pending on openSUSE ... > I read that as the "upstream" is not maintained, so it is up to individual > distributions to patch their own copies (?) Yes. After all, thats one of the major reasons for distributions to exist (do the work otherwise each individual user has to do). Fix ships with the next openSUSE TW release. |